Make Com Israeli Automations

Make.com Israeli Automations

Instructions

Step 1: Identify the Scenario Pattern

Before building any scenario, map the business workflow to a Make.com pattern. Israeli business automations fall into predictable categories:

Choose the pattern based on these criteria:

• Real-time needed? Use webhooks (instant triggers). Otherwise, use scheduled polling.
• Multiple destinations? Use a Router module to branch the flow.
• Processing a list? Use an Iterator to loop over items (e.g., line items on an invoice).
• Aggregating data? Use an Array Aggregator before the final output.
• AI decision needed? Use Make.com AI Agents with Module Tools (see Step 8).

Step 2: Configure Israeli App Connections

Morning (formerly Green Invoice / Hashbonit Yeruqa)

Morning has a community-built Make.com module, created by Callbox and listed as "Morning by Callbox" on the Make.com marketplace. Make.com states: "Make does not maintain or support this integration." The module requires a Best subscription tier or higher.

To set up the connection:

1. In Make.com, search for "Morning" in the module palette (NOT "Green Invoice")
2. Create a connection using your Morning API key and secret (from Morning dashboard: Settings > API Integration)
3. The API domain remains api.greeninvoice.co.il despite the rebrand

Available actions (there are NO watch/trigger modules):

The module's action list (Add Client, Add Document, Add Expense, the Get All / Search variants, Update and Delete Client, plus the raw Make an API Call) is tabulated with its key parameters in references/make-israeli-modules.md. Note that Callbox now also exposes Add Supplier, Add Expense Draft by File, Get Document and Get a Preview Document.

Since there are no triggers, use one of these patterns for event-driven scenarios:

• Scheduled polling: Use "Search Documents" on a schedule (e.g., every 15 minutes) filtered to recent documents
• External webhook: Have another system (e.g., your app) call a Make.com Custom Webhook when a document is created

Key field mappings for Morning documents:

The Morning field mapping (document type codes, currency, vatType, lang) is tabulated in references/make-israeli-modules.md. Two that cause real damage if guessed: income[].price is in decimal shekels, not agorot (price: 50 is 50 shekels), and type is a numeric code (305 = tax invoice, 320 = tax invoice/receipt, 400 = receipt).

Israel Invoice Reform 2026 (threshold step-down): Tax invoices over the threshold require a Tax Authority allocation number (mispar haktza'a). The threshold drops in 2026:

Morning's API supports the allocation number via the allocationNumber field. For invoices above the current threshold, your scenario must either:

1. Request an allocation number from the Tax Authority API before creating the document
2. Use Morning's built-in allocation flow (if enabled in your Morning account settings)

Compare the amount BEFORE VAT. The Tax Authority states the requirement applies "כשסכום העסקה לפני מע"מ גבוה מ-5,000 ₪". A scenario that tests the gross document total requests an allocation number on every invoice between roughly 4,238 and 5,000 NIS net that does not need one.

What actually happens without one: the allocation number is a condition for the RECIPIENT deducting input VAT (יידרשו כתנאי לניכוי מס התשומות), not a condition of the invoice's validity. The invoice is not void; the buyer simply cannot deduct מס תשומות. That difference decides who your automation has to alert, and when.

Hold the threshold in a workflow variable rather than hardcoding it. The published schedule ends at 5,000 NIS from 1 June 2026 and no further step-down has been legislated, so this is for maintainability, not because another drop is scheduled.

iCount

iCount has a native Make.com module (first-party supported). This is a significant option for Israeli accounting automation.

Available actions include:

• Create/manage expenses, leads, tasks, events
• Inventory management
• Client management
• Create documents (invoices, receipts, quotes)

To set up: search "iCount" in the module palette, connect with your iCount API credentials.

Monday.com

Monday.com has a native Make.com module. Israeli businesses commonly use it for project billing.

Important (API versioning): monday.com does not version its API as v1/v2. api.monday.com/v2 is the GraphQL ENDPOINT path, and it has not changed. The API version is date-based (2026-07 is the current default; 2026-04 is in maintenance and 2026-10 is a release candidate), selected per request with an API-Version header. Pin an explicit version rather than riding the default, and track the deprecation notices: monday states that "Each version deprecation will be announced at least six months in advance".

1. Use "Watch Items" as trigger (set to a specific board)
2. Map column values using the column ID (not the title, since titles may be in Hebrew and can be renamed)
3. For status columns, use the label index (not the Hebrew label text) for reliable matching

Priority ERP

Priority has a community-built Make.com module available on the marketplace. Search for "Priority" in the module palette. Alternatively, use HTTP modules for full control.

For the community module:

1. Search "Priority" in Make.com modules
2. Connect with your Priority credentials

For HTTP module approach:

1. Add an HTTP "Make a request" module
2. URL pattern: https://{your-priority-domain}/odata/Priority/tabula.ini/{company}/{entity}
3. Authentication options: Basic Auth, Personal Access Token (PAT), or OAuth2 (Priority supports all three)
4. Set header Content-Type: application/json
5. For Hebrew field values, ensure the request body is UTF-8 encoded

The common Priority entities for Israeli scenarios (ORDERS, AINVOICES, PORDERS, LOGCOUNTERS) are listed with their OData paths in references/make-israeli-modules.md.

WhatsApp Business

Make.com has a native first-party WhatsApp Business Cloud module. Use this instead of the HTTP module approach for simpler setup and built-in error handling.

Available triggers and actions:

• Watch Events (trigger): Receives incoming messages, status updates
• Send a Message: Send text, image, document, or location messages
• Send a Template Message: Send pre-approved template messages (required for outbound initiation)

To set up:

1. Connect your Meta Business account in Make.com
2. Select your WhatsApp Business phone number
3. For Hebrew templates, set the template language to he

For advanced use cases not covered by the native module, use the HTTP module with the WhatsApp Cloud API. Use the latest API version (check Meta's changelog rather than hardcoding a version number).

Israeli SMS Providers (via HTTP module)

For SMS automation (019, InforUMobile, SMS4Free):

Consult references/make-israeli-modules.md for full endpoint specs, authentication details, and payload examples.

Step 3: Handle Hebrew Data

Text Parsing and Transformation

When processing Hebrew text in Make.com:

• Use the toString function to safely handle Hebrew string values from API responses
• For regex on Hebrew text, use Unicode character classes: \p{Hebrew} matches Hebrew letters
• When concatenating Hebrew and English (e.g., invoice references), place the Hebrew segment first to maintain RTL reading order
• Use trim on Hebrew text fields, as some Israeli APIs pad with invisible Unicode characters (LTR/RTL marks)

ILS Currency Formatting

Make.com's formatNumber function handles ILS:

Note: the Shekel sign is Unicode U+20AA. Do not use NIS as a symbol in customer-facing output.

Hebrew Date Conversion

Make.com stores dates in ISO 8601 format. For Hebrew display:

• Use formatDate(date; "DD/MM/YYYY") for Israeli date format (day/month/year)
• For Hebrew month names, Make has no native Hebrew month formatting. Get the numeric month with formatDate(now; "M") and map it with a switch function or a Set Variable lookup; the full 12-row table is in references/make-israeli-modules.md under "Hebrew Month Names".

Step 4: Build Router Patterns for Israeli Billing Cycles

Israeli businesses follow specific billing cycles that differ from US/EU patterns. Use Make.com Routers to branch logic based on these cycles.

Bimonthly VAT Reporting (Doch Du-Hodshi)

VAT reports are filed bimonthly for most businesses (businesses under the threshold file annually). The VAT periods are:

Build a Router with 6 branches, each filtering invoices for the relevant period. After the router, use an Array Aggregator to sum amounts per period for the VAT report.

Use a Make.com Data Store to track which periods have been processed and prevent duplicate runs. See Step 7 for Data Store configuration details.

Bimonthly Advance Tax Payments (Mikdamot)

Self-employed and some companies pay bimonthly advance tax (mikdamot), aligned with the same bimonthly VAT reporting periods. The advance payment is due by the 15th-19th of the month following each period:

The advance payment is typically a percentage of revenue set by the Tax Authority (commonly 5-15% for new businesses). Store the advance rate in a Make.com Data Store or Set Variable module, since it varies per business and is updated annually.

Annual Reporting

Annual tax return deadlines vary by filing method:

• Online filing: April 30
• Accountant filing: extended to May 31 or later (varies by year)

For annual automations, schedule a scenario to run on January 1 that aggregates the previous year's data.

Consult references/billing-cycle-patterns.md for detailed router configurations.

Step 5: Schedule with the Israeli Calendar

Shabbat-Aware Scheduling

Make.com scenarios that interact with Israeli businesses or customers should avoid running during Shabbat (Friday sunset to Saturday sunset). The recommended approach is to use the Hebcal community module available on Make.com (no API key required):

1. Search for "Hebcal" in the Make.com module palette (community module at apps.make.com/hebcal-ryuwr8)
2. Use the Hebcal module to check if today is Shabbat or a holiday
3. Add a Filter module after Hebcal to stop execution on Shabbat/holidays

For a simpler (but less precise) approach, use scheduling settings:

1. Set the scenario schedule to run Sunday through Thursday only
2. For Friday runs, set the latest execution time to 14:00 Israel time (IST, UTC+2 / IDT, UTC+3 during DST)
3. Avoid Saturday entirely

In Make.com scheduling settings:

• Use the "Specify dates" option and exclude Saturday
• Set timezone to Asia/Jerusalem

Note: A 14:00 Friday cutoff is a safe conservative default. For precise candle-lighting times, the Hebcal community module is the better choice since it accounts for seasonal variation and specific location.

Israeli Holiday Detection

Use the Hebcal community module for holiday detection. It handles Rosh Hashana, Yom Kippur, Sukkot, Pesach, Shavuot, and other holidays without requiring an API key or HTTP module configuration.

If you need more control, you can use the Hebcal REST API via HTTP module:

https://www.hebcal.com/hebcal?v=1&cfg=json&year=now&month=now&maj=on&geo=pos&latitude=32.0853&longitude=34.7818

Parse the response for today's date. If a major holiday ("category": "holiday") is found, use a Filter module to stop execution.

Business Hours (Sunday-Thursday)

Israeli business hours are typically Sunday through Thursday, 09:00-18:00. For B2B automations:

• Schedule runs between 09:00-17:00 IST
• Use Sunday as the first day of the business week
• Friday is a half-day (until ~13:00)

Step 6: Handle Webhooks from Israeli Payment Gateways

Cardcom Webhook

Cardcom has two webhook generations with different field names, confirm which your terminal uses:

• API v11 (current): posts a JSON body. Success is ResponseCode = 0 (with Description), plus TranzactionId and Amount; card-owner/token data are nested. Verify exact field names against the v11 docs (https://secure.cardcom.solutions/Api/v11/Docs), do not assume the legacy names below.
• Legacy LowProfile (v10): posts form-encoded Name-to-Value fields (redirect IndicatorUrl is a GET). The table below is this v10 set.

1. Create a Custom Webhook trigger in Make.com
2. Set Cardcom's "Notify URL" to the Make.com webhook URL
3. Legacy LowProfile (v10) callback fields:

The legacy LowProfile (v10) field set (OperationResponse, Amount, CardOwnerID, NumOfPayments, Token) and the v11 JSON field names are tabulated in references/make-israeli-modules.md. Confirm which generation your terminal uses before mapping fields.

Tranzila Webhook

Tranzila uses a redirect-based flow. To capture results:

1. Create a Custom Webhook trigger
2. Set Tranzila's notify_url parameter
3. Key fields:

The Tranzila notify fields (Response, sum, ccno, myid, and the installment trio fpay / spay / npay) are tabulated in references/make-israeli-modules.md. The one that catches people: npay is the number of ADDITIONAL payments, so total installments = npay + 1.

Tranzila API v2 introduces iframe-based hosted payment fields for PCI compliance and supports Bit payments.

Grow (by Meshulam) Webhook

Grow is an independent fintech company by Meshulam (NOT affiliated with Bank Leumi).

Grow sends webhook notifications as JSON POST. To verify authenticity, check the webhookKey field in the JSON payload body (not a header signature). Grow's API uses multipart/form-data for outbound requests, not JSON.

1. Register your Make.com webhook URL in the Grow dashboard
2. Grow sends JSON POST with event type and payment details
3. Verify the webhook by comparing the webhookKey value in the JSON body against your configured key

Bit (by Bank HaPoalim)

Bit is Israel's dominant P2P payment platform and has a business API. For Bit Business webhooks:

1. Register for Bit Business API access
2. Configure webhook URL in the Bit Business dashboard
3. Bit sends payment notifications for completed transactions

Additional Gateways

• PayMe (by Isracard): Payment processing with installment support. Configure webhook URL in PayMe dashboard.
• PayBox: Digital payment solution with webhook notifications.

For all payment gateways, always validate:

• The response/status code indicates success before processing
• The amount matches the expected charge
• For installments (tashlumim), store both the total and per-payment amounts

Step 7: Use Data Store for VAT Period Tracking

Make.com Data Store provides persistent storage for tracking billing periods across scenario runs. This prevents duplicate processing and gives you an audit trail.

Create a Data Store with these fields:

Usage pattern:

1. At the start of each billing scenario, use "Search records" to check if the current period is already processed
2. If status is completed or filed, skip execution
3. If status is pending or missing, proceed with the scenario
4. After processing, update the record status to completed with the aggregated totals

This is especially important for VAT scenarios, since accidentally processing the same period twice would generate incorrect reports.

Step 8: Make.com AI Agents

Make.com launched AI Agents in April 2025, with Visual AI Agents in the Scenario Builder released in 2026. This enables AI-powered decision making within your Israeli business automations.

Key capabilities:

• Module Tools: Any Make.com module can be exposed as a tool for the AI Agent. For example, the Morning module's "Search Documents" action can be a tool the agent uses to look up invoice data before deciding what to do.
• Multi-modal support: AI Agents can process PDFs, images, and CSVs, useful for extracting data from Hebrew invoices or scanned documents.
• Reasoning Panel: Debug and inspect the AI Agent's decision-making process.

Israeli business use cases for AI Agents:

To set up an AI Agent scenario:

1. Add an AI Agent module to your scenario
2. Configure the agent's instructions (supports Hebrew instructions)
3. Add Module Tools by selecting existing modules in your scenario
4. The agent decides which tools to call based on the input context

Step 9: Expose Scenarios as MCP Tools (Make.com MCP Server)

Make.com runs a hosted MCP server that lets AI agents (Claude Code, Cursor, and other MCP clients) call your Make scenarios as tools, turning an Israeli automation you have already built (a Morning invoice creator, a bimonthly VAT summary) into a tool an agent can invoke directly.

Connect via OAuth (https://mcp.make.com, nothing to store) or an MCP token (https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN>). The scenario-run scope is on all plans; the management scope needs a paid plan. For a scenario to appear as a tool it must be active, set to on-demand scheduling, and have defined inputs, outputs, and a detailed description (Hebrew descriptions work). Scenario-run tools time out at 25s (OAuth) or 40s (token); longer runs return an executionId to poll with executions_get.

Consult references/make-mcp-server.md for the connection-method details, the Claude Code config blocks, the scope table, and Israeli use cases.

Step 10: When to Use Make.com vs Alternatives

Choose Make.com when: the team is non-technical, you need visual debugging, and you want community modules for Israeli services. Choose n8n when: you need self-hosting, full code control, or cost-free operation. Choose Zapier when: you only need simple 2-step automations between mainstream apps.

Examples

Example 1: Sync Morning to Monday.com

User says: "Create a Make.com scenario that adds a new Monday.com item whenever a Morning tax invoice is created"

Actions:

1. Add Morning "Search Documents" action on a 15-minute schedule, filtered to type 305 (tax invoice) and recent creation date
2. Add Monday.com "Create an Item" action
3. Map fields: invoice number to Name column, client name to Client column (by column ID), amount to Amount column (number type, already in shekels), date to Date column using formatDate
4. Set schedule to every 15 minutes, Sunday-Thursday + Friday until 14:00, timezone Asia/Jerusalem

Result: New Monday.com items created automatically for each tax invoice, with Hebrew client names preserved and ILS amounts correctly formatted.

Example 2: Bimonthly VAT Summary

User says: "Build a scenario that generates a VAT summary spreadsheet at the end of each bimonthly period"

Actions:

1. Schedule trigger for the 1st of March, May, July, September, November, January
2. Check Data Store for period status (skip if already processed)
3. Add Morning "Search Documents" to fetch all documents from the previous 2-month period
4. Add Iterator to process each document
5. Add Router with branches for income (type 305, Tax Invoice) and credit notes (type 330, Credit Note)
6. Add Array Aggregator per branch to sum amounts
7. Add Google Sheets "Add Row" to write period, total income, total credits, and VAT difference
8. Update Data Store record with status completed and totals

Result: Automated bimonthly VAT summary that matches the Israeli tax authority reporting periods, with Data Store preventing duplicate processing.

Example 3: WhatsApp Order Confirmation in Hebrew

User says: "Send a WhatsApp message in Hebrew when a customer places an order"

Actions:

1. Add Custom Webhook trigger to receive order events
2. Add WhatsApp Business Cloud "Send a Template Message" action (native module)
3. Select a pre-approved Hebrew message template with variables: customer name, order number, total in ILS
4. Format amount with "₪" + formatNumber(amount; 2; "."; ",")
5. Use Hebcal community module + Filter to queue messages during Shabbat for delivery on Sunday morning

Result: Customers receive Hebrew WhatsApp confirmations with properly formatted ILS amounts, respecting Shabbat hours.

Example 4: AI Agent for Invoice Processing

User says: "Set up an AI agent that reads email attachments and creates the right type of document in Morning"

Actions:

1. Add Gmail "Watch Emails" trigger filtered to emails with attachments
2. Add Make.com AI Agent module with Hebrew instructions: classify the attachment as invoice, receipt, quote, or credit note
3. Add Morning "Add Document" as a Module Tool, with type parameter mapped from the agent's classification (305 = Tax Invoice, 320 = Tax Invoice/Receipt, 400 = Receipt, 10 = Price Quote)
4. Add Morning "Search Clients" as a Module Tool so the agent can look up existing clients
5. Add an error handler route for unclassifiable documents

Result: AI-powered document processing that automatically classifies Hebrew invoices and creates the correct document type in Morning.

For a worked example of exposing a Morning invoice scenario as an MCP tool callable from Claude Code, see references/make-mcp-server.md.

Bundled Resources

References

• references/make-israeli-modules.md - Complete reference of Israeli service modules and HTTP configurations for Make.com, including Morning (formerly Green Invoice), iCount, Monday.com, Priority ERP, WhatsApp Cloud API, Israeli SMS providers, and payment gateways. Consult when setting up a new Israeli app connection or troubleshooting API authentication.
• references/billing-cycle-patterns.md - Detailed Israeli billing cycle automation patterns including bimonthly VAT, bimonthly advance payments, annual reporting, and payroll schedules. Includes Make.com Data Store configurations and router patterns. Consult when building time-based automations tied to Israeli tax or billing deadlines.
• references/make-mcp-server.md - Make.com MCP server reference: OAuth and MCP-token connection methods, Claude Code config blocks, scopes, the active + on-demand requirement for exposing a scenario as a tool, timeout behavior, and Israeli use cases. Consult when wiring a Make scenario into an AI agent as an MCP tool.

Gotchas

• Agents default to monthly VAT reporting (US/EU pattern). Israeli VAT reporting is bimonthly for most businesses. Always confirm the reporting frequency before building period filters.
• Morning (Green Invoice) amounts in the API are in decimal shekels (e.g., price: 50 means 50 shekels). Do NOT multiply by 100 or convert to agorot. This is different from some payment gateway APIs.
• The Morning Make.com module is community-built by Callbox, not maintained by Make.com. It has no trigger/watch modules, only actions. Plan for scheduled polling instead of event-driven triggers.
• Morning document type codes: 10 = Price Quote, 305 = Tax Invoice, 320 = Tax Invoice/Receipt, 330 = Credit Note/Refund, 400 = Receipt.
• Tranzila's npay field means the number of additional payments, not total payments. Always use npay = total_installments - 1.
• Make.com's date functions use US-style day-of-week numbering (0 = Sunday). Agents often assume Monday = 0 (ISO 8601). Sunday is 0, Saturday is 6 in Make.com.
• Agents tend to schedule Friday runs at 17:00 or later. Shabbat can start as early as 16:00 in winter. Use 14:00 as the safe Friday cutoff, or better, use the Hebcal community module for precise times.
• Hebrew column names in Monday.com should be referenced by column ID, not by the display title. Agents often try to use the Hebrew title directly, which breaks when users rename columns.
• Make.com filters use a visual UI with dropdown operators, not code syntax. There is no = vs == distinction since you select "equal to" from a dropdown.
• The Israeli tax year is January-December (same as calendar year), but agents sometimes assume April-March (UK pattern) or October-September (US fiscal year).
• Invoice Reform 2026 affects automation, and the comparison is made BEFORE VAT. Tax invoices over the threshold (10,000 NIS through 31 May 2026, then 5,000 NIS from 1 June 2026) require a Tax Authority allocation number. The Tax Authority phrases it as כשסכום העסקה לפני מע"מ גבוה מ-5,000 ₪, so a scenario that filters on the gross document total over-requests on every invoice between roughly 4,238 and 5,000 NIS net. Note also what the number is FOR: it is a condition of the recipient's input-VAT deduction, not of the invoice's validity. Hold the threshold in a scenario variable rather than a literal.
• monday.com has no v1/v2 API split. api.monday.com/v2 is the GraphQL endpoint path; the API version is date-based (2026-07 current) and set per request with an API-Version header. Pin one explicitly rather than inheriting whatever the default becomes.
• A Make scenario only appears as an MCP tool when it is both active AND set to on-demand scheduling. Agents often satisfy only one condition; a scheduled or instant-trigger scenario will never show up in the MCP tool list.
• MCP scenario-run tools time out at 25s (OAuth) or 40s (token). A longer scenario returns an executionId instead of the result, poll with executions_get using that ID rather than treating the timeout as a failure.

Troubleshooting

Error: "Morning API returns 401 Unauthorized"

Cause: API key/secret mismatch, or using sandbox credentials in production (or vice versa) Solution: Verify you are using the correct environment. Morning sandbox URL is https://sandbox.d.greeninvoice.co.il/api/v1/, production is https://api.greeninvoice.co.il/api/v1/. Regenerate the API key if needed. Note: the API domain still uses greeninvoice.co.il despite the Morning rebrand.

Error: "Hebrew text appears garbled in output"

Cause: Encoding mismatch. Some Israeli APIs return Windows-1255 or ISO-8859-8 instead of UTF-8. Solution: Check the API response headers for charset. If not UTF-8, add a Text Parser module after the HTTP module and set input encoding to match the source. Morning (Green Invoice) and Monday.com use UTF-8 natively.

Error: "Make.com scenario runs on Saturday"

Cause: Timezone set to UTC instead of Asia/Jerusalem, causing the schedule to misalign with Israeli time. Solution: In scenario settings, set timezone to Asia/Jerusalem. Use the Hebcal community module for reliable Shabbat detection rather than manual day-of-week checks.

Error: "Cardcom webhook not triggering"

Cause: Make.com custom webhook must be "listening" (turned on) before Cardcom sends the notification. Also, Cardcom requires HTTPS. Solution: Ensure the scenario is active and the webhook is in listening mode. Copy the webhook URL after activating it. Verify the URL starts with https://. Test with a small transaction first.

Error: "Morning module not available in Make.com"

Cause: The Morning module requires the Best subscription tier or higher. It is a community module, not included in Free or Core plans. Solution: the Callbox app page states the module "requires a best or higher subscription and an api key". Note that "Best" is not a tier in Make's current lineup (Free / Core / Pro / Teams / Enterprise), so treat it as legacy wording and check what the app store shows against your own account rather than shopping for a plan by that name. The alternatives avoid the question entirely: use the "Make an API Call" action from the Morning module, call the Morning REST API through a generic HTTP module, or use iCount, which has a native first-party Make module with no community-app tier gate.

Error: "Invoice rejected: missing allocation number"

Cause: Invoices over the Invoice Reform threshold require a Tax Authority allocation number. The threshold is 10,000 NIS through May 31, 2026, then drops to 5,000 NIS on June 1, 2026. Solution: Add a Filter module before document creation that compares the amount BEFORE VAT against a workflow variable holding the current threshold (hold it in a variable for maintainability; the published schedule ends at 5,000 NIS from 1 June 2026 and no further drop has been legislated). If the amount exceeds the threshold, request an allocation number first, then pass it in the allocationNumber field when creating the document.

Error: "Make scenario does not appear as an MCP tool"

Cause: The scenario is not active, is not set to on-demand scheduling, or the MCP connection is missing the scenario-run scope. Solution: Set the scenario to active status AND on-demand scheduling, both are required. Confirm the MCP connection has the "Run your scenarios" scope (OAuth) or the mcp:use scope (token). If the tool list is stale, reconnect the MCP client to refresh it.