misim-tax-research

Israeli Tax Reporting & Payment Deadlines

tax_deadlines_il

Read-onlyIdempotent

Return the actual due dates for periodic Israeli reporting and payment — VAT and income-tax advances, income-tax withholding, the detailed VAT report, and National Insurance where the year's notice covers it — with the reason for any postponement. Approved calendars: 2026, from the Tax Authority notice of 15.10.2025, verified by a CPA; and 2027, from the notice of 13.10.2026, which sets no National Insurance dates. Defaults to 2026 until 01.01.2027, then 2027. Filter by workflow, obligation or reporting month. Years without an approved calendar, and annual returns, return no dates and say so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tax_deadlines_il"
  }
}

Input Schema

Name	Required	Description
`tax_year`	No	Tax year of the reporting periods. Approved calendars: 2026, from the Tax Authority notice of 15.10.2025, and 2027, from the notice of 13.10.2026. Defaults to 2026 until 01.01.2027, then 2027. National Insurance dates exist for 2026 only — the 2027 notice does not set them. Other years return no dates.
`workflow`	No	Filing workflow. vat-reporting → VAT/advances and the detailed VAT report; withholding-reporting → income-tax withholding. Omit (with no obligation) for all periodic obligations.
`obligation`	No	One periodic obligation; overrides the workflow mapping.
`period_month`	No	Reporting period month (1 = January). The due date falls in the following month.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is free; the description adds real value beyond it — data provenance (Tax Authority notice of 15.10.2025 and 13.10.2026, CPA-verified), the defaulting rule and its switchover date (01.01.2027), the partial 2027 coverage for National Insurance, return of postponement reasons, and explicit empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then coverage, then defaulting, then filtering, then edge cases — a logical order. Almost every clause carries information, though the long em-dash-heavy sentences and the interleaving of coverage facts with provenance details make it denser than needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by saying it returns due dates with the reason for any postponement, plus what an empty response means. It does not describe the record shape (e.g., one row per obligation per month), which leaves a small return-format gap for a zero-required-parameter query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters including enum meanings and the override rule. The description adds only the combining semantics ('Filter by workflow, obligation or reporting month'), which the per-parameter schema text largely covers. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Return the actual due dates for periodic Israeli reporting and payment' — and enumerates exactly which obligations are covered (VAT and advances, withholding, detailed VAT report, National Insurance). No sibling tool returns statutory deadlines, so it is trivially distinguishable from the calculators and form helpers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit negative guidance: years without an approved calendar and annual returns 'return no dates and say so', and National Insurance dates only exist where the notice covers them (2026 yes, 2027 no). It states the default year and when that default flips. It stops short of naming alternatives for the calculator/return-helper siblings, so not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All misim-tax-research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?