Skip to main content
Glama

What PAYE deadline calculator, 2026/27 and 2027/28 computes

calculator_describe

The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 content returned (inputs, outputs, assumptions, tables) but does not state that the tool is read-only, does not perform calculations, or what its response format looks like. For a no-parameter describe endpoint, this is a noticeable gap.

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 compact sentence covering the key returned categories. It is efficiently sized, though it front-loads a noun phrase rather than an action verb, making it slightly less scannable.

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 no-param, no-output-schema describe tool, the description identifies the main categories of information returned. However, it omits the tax years (2026/27 and 2027/28) that are central in the title, and it does not explicitly clarify that this tool provides metadata rather than performing calculations.

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 has zero parameters, so the baseline score of 4 applies. The schema is empty and the description appropriately does not discuss parameters because none exist.

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

Purpose3/5

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

The description is a noun phrase listing what the tool surfaces ('inputs... outputs... assumptions and tables') rather than a clear verb+resource statement. The title supplies context about the PAYE deadline calculator, but the description alone does not explicitly say it describes the calculator's metadata. It is distinguishable from 'calculate' only by inference.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus the sibling 'calculate' tool. An agent can infer it is a pre-computation documentation lookup, but the description never states that. No alternatives or exclusions are mentioned.

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