Skip to main content
Glama

compliance_deadlines

Read-only

When statutory returns and payroll filings are due, per country. Covers IN (GSTR-1/3B/9/9C, CMP-08, Form 24Q, Form 16, PF ECR, ESI), AU (BAS, STP, Super Guarantee), GB (VAT MTD, RTI, Self Assessment), US (1099-NEC/MISC, W-2, Form 941/940), CA (T4, GST/HST). Optional country, frequency, and form filters. Note: dates rotate annually — every response carries a disclaimer with the per-deadline source URL for authority confirmation.

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": "compliance_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoSubstring match against form name, e.g. "GSTR-3B", "BAS", "1099", "T4". Case-insensitive.
countryNoISO country code. Filters to one country (IN, AU, GB, US, CA covered today).
frequencyNoFiling cadence. Useful for "what are my monthly returns" style queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish read-only, non-open-world behavior, and the description adds meaningful operational caveats: dates rotate annually and every response includes a disclaimer with a per-deadline source URL for authority confirmation. It does not describe pagination or the full response shape, but the key reliability caveat is disclosed.

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?

The purpose is front-loaded, and the coverage list, filter note, and annual-rotation caveat are presented in a compact paragraph. The form enumeration is dense but relevant to coverage and filter selection, so it generally earns its space.

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?

For a read-only, three-filter lookup with no output schema, the description covers the purpose, supported jurisdictions and forms, available filters, and the annual-rotation/source-URL caveat. The main remaining gap is that it does not describe response fields beyond the disclaimer and source URL, but it is sufficient for correct invocation.

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 the three optional filters, their enums, and the form substring matching behavior. The description's coverage list and filter sentence add useful context about supported countries and forms, but they do not add syntax or edge-case guidance beyond the schema.

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

Purpose4/5

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

The description clearly states that the tool provides statutory return and payroll filing due dates per country, and it lists the supported jurisdictions and forms. It is not explicitly differentiated from siblings such as next_deadlines or compliance_capabilities, but the core purpose is unambiguous.

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?

The first sentence establishes clear usage context: looking up when statutory returns and payroll filings are due by country. It also mentions the optional country, frequency, and form filters, though it does not provide explicit exclusions or named alternatives.

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