Skip to main content
Glama

Tidy Quid budget planners

UK money dates 2026/27

uk_money_dates
Read-onlyIdempotent

Key UK personal-finance dates for the 2026/27 tax year: tax year start and end, Self Assessment deadlines (31 January 2027), payments on account, ISA allowance and Making Tax Digital thresholds, each with GOV.UK sources.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds useful context by stating each entry carries GOV.UK sources, which tells the agent the output is citable and authoritative. It does not disclose the return format (list vs. object), any staleness/currency caveat, or that it is a static, parameterless reference.

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

Conciseness5/5

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

A single front-loaded sentence with the subject (UK money dates 2026/27) first and the coverage list after. Every clause carries information — no filler, no repetition of the title.

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, so the description usefully enumerates the contents the agent will receive, which is the main thing it must know. Minor gaps remain: the format of the results and the fact that data is fixed to the 2026/27 tax year (no other years available) are only implied.

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 tool takes zero parameters, so the schema-level baseline of 4 applies; there is nothing parameter-related the description needs to compensate for. No meaning is added or lost.

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 names a specific resource — UK personal-finance dates for the 2026/27 tax year — and enumerates exactly what it covers (tax year start/end, Self Assessment 31 Jan 2027, payments on account, ISA allowance, MTD thresholds). It lacks an explicit verb and never contrasts itself with the sibling tools, but the enumerated scope is specific enough that an agent can tell what it returns.

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?

Usage is only implied: an agent should call it when it needs UK tax-year reference dates. There is no explicit when-to-use / when-not-to-use guidance and no naming of alternatives (e.g. uk_budget_check) or the condition that would select one over the other.

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