Skip to main content
Glama

tax_deadlines

PRO. Upcoming HMRC and Companies House deadlines for the next N months; add company_year_end for Corporation Tax, CT600 and accounts dates.

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

Input Schema

NameRequiredDescriptionDefault
monthsNo
access_tokenNoSubscriber token from /success (or Authorization: Bearer)
company_year_endNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the paid 'PRO' context and the scope of deadlines returned, but it does not clarify whether the operation is read-only, how authentication/access tokens are required, whether results are paginated, date inclusivity, or the response shape. This is thin for a tool with zero annotation coverage.

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 description is a single, front-loaded sentence with no wasted text, and the key purpose and optional extension are stated up front. The leading 'PRO.' is terse and somewhat cryptic, which slightly reduces clarity, but overall it is appropriately sized.

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

Completeness3/5

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

For a three-parameter read-style deadline tool with no output schema and no annotations, the description covers the core purpose and the company_year_end extension adequately. It remains incomplete regarding authentication requirements, return format and whether months defaults or constraints exist, so it is minimally viable rather than fully complete.

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

Parameters4/5

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

The description adds meaning beyond the schema for two parameters: 'months' is explained as the next N months, and company_year_end is tied to Corporation Tax, CT600 and accounts dates. The access_token parameter is already documented in the schema, and overall the description compensates reasonably well for the 67% schema coverage, though it does not explain constraints on the months value.

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 identifies the resource and scope: upcoming HMRC and Companies House deadlines for the next N months, plus Corporation Tax, CT600 and accounts dates when company_year_end is supplied. It is specific enough for an agent to understand the tool's purpose, though it does not explicitly distinguish itself from siblings such as due_date or month_planner.

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

Usage Guidelines3/5

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

The description implies when to use the tool by framing it around upcoming HMRC and Companies House deadlines, and it notes that adding company_year_end expands results to Corporation Tax, CT600 and accounts dates. However, it does not explicitly state when to choose this over alternatives like due_date or month_planner, nor does it describe any exclusions.

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.