Skip to main content
Glama

Statutory filing deadlines

get_filing_deadlines
Read-onlyIdempotent

PAID ($0.005, same as any series). Recurring statutory tax deadlines for a country — VAT/GST returns and payments, PAYE/payroll withholding remittances, corporate income tax returns and provisional/instalment payments — as RULES, each cited to the official source with the verbatim phrase that states it, plus the actual DUE DATES in a window, rolled for the country's weekend and national public holidays (every skipped day is listed). Where a rule's source does not say which way a weekend deadline moves, the date is flagged roll_unverified rather than guessed. Countries or taxes we could not verify are returned as a free coverage_gap with reasons, never invented. Pass year_end (MM-DD) to re-anchor corporate-tax rules on the company's own accounting year end. The HTML page /{country}/filing-deadlines shows the rules free. Every AE series is free to try. After a 200, bind get_changes (free poll) or register_alert (HMAC push; Register: $0 · Delivery after trial: $0.10) on this series so a later gazette does not silently retire the value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoWindow end, YYYY-MM-DD. Default from + 365 days; at most 400 days after from
taxNoOnly this tax's rules and dates
fromNoWindow start, YYYY-MM-DD. Default today
api_keyNoAPI key (bypasses x402; metered for invoicing)
countryYesISO country code
year_endNoCompany accounting year end, MM-DD (e.g. 06-30). Applies to rules marked year_end_variable

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapsNo
unitNo
errorNoPresent on a free refusal or error; no charge
notesNo
staleNo
valueNoThe rules. Each carries its own source {name, url, anchor} and last_confirmed
seriesNo
sourceNo
statusNoOn a coverage gap: researched_no_verified_rule or not_yet_researched
countryNo
due_datesNoComputed occurrences in the window, sorted by due_date
no_chargeNo
price_usdNo
confidenceNo
disclaimerNo
how_to_payNo
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
x_next_bindNo
coverage_gapsNoTaxes in scope with no verified rule for this country, and why
http_endpointNo
coverage_labelNoHow much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
effective_fromNo
last_confirmedNo
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card
computed_disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations establish the safe-read profile (readOnlyHint, idempotentHint, destructiveHint false), yet the description adds substantial behavior beyond them: holiday/weekend rolling with every skipped day listed, the roll_unverified flag when sources are ambiguous, coverage_gap for unverifiable countries, verbatim source citations, and paid pricing ($0.005). It also discloses what to do after a 200 response.

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

Conciseness3/5

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

The core purpose and behavior are present but the description is dense and opens with pricing rather than the tool's function. Marketing sentences ('Every AE series is free to try') and repeated pricing details dilute the front-loaded value, though the rolling/coverage_gap sentences earn their place.

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

Completeness5/5

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

For a complex paid tool with an output schema, the description covers the domain thoroughly: rule structure, citation practice, holiday rolling, edge-case flags, coverage gaps, year_end re-anchoring, and post-call subscription guidance. An agent has what it needs to invoke and interpret results correctly.

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 baseline is 3. The description adds only marginal meaning for year_end ('re-anchor corporate-tax rules on the company's own accounting year end'), which the schema already conveys via 'Applies to rules marked year_end_variable'; from/to/tax/country are left entirely to the schema.

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: 'Recurring statutory tax deadlines for a country,' enumerating VAT/GST returns, PAYE withholding remittances, and CIT returns/provisional payments as RULES plus due dates. This is clearly distinguishable from sibling computational tools like compute_vat or compute_income_tax.

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?

Names two follow-up alternatives (get_changes for polling, register_alert for push) and mentions the free HTML page as an alternative for viewing rules. It also explains the year_end parameter's use case, but does not explicitly state when to prefer this tool over the numerous sibling computation tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources