calculator_describeThe inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of disclosure. It does inform the agent that the tool returns information about inputs, outputs, assumptions, and tables, which gives some behavioral transparency. However, it does not explicitly state that the tool performs no calculation or side effects, or describe how the output is presented.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that efficiently enumerates the full scope of the tool's output: inputs, outputs, assumptions, and tables. There is no wasted wording or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless describe tool with no output schema, the description adequately captures what an agent will receive. It names the major content categories without promising excessive detail. It could be slightly stronger by noting when to call it relative to calculate, but overall it is sufficiently complete for the tool's simple nature.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema confirms an empty properties object, so there is nothing for the description to clarify. The description does promise to explain inputs with units, ranges, and defaults, which is accurate and helpful context for the tool's overall purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (Section 877A exit tax calculator) and specifies what the tool covers: inputs, outputs, assumptions, and tables. It is distinguishable from sibling tools like calculate and enquiry_describe because it focuses on describing the calculator's behavior rather than performing a calculation. It lacks an explicit verb like 'returns' or 'describes,' but the intent is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives such as calculate or enquiry_describe. An agent must infer that this tool is useful before invoking calculate or for understanding calculator internals, but the description does not state this explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct role: calculate performs the tax computation, calculator_describe and enquiry_describe explain the respective flows, enquiry_fields provides the input schema, and submit_enquiry is the only mutating action. No two tools appear to overlap in purpose.
Names are readable and lowercase but mix verb-first conventions (calculate, submit_enquiry) with noun-first descriptors (calculator_describe, enquiry_describe, enquiry_fields). The 'describe' and 'fields' suffixes are internally consistent, but there is no uniform verb_noun pattern across the set.
Five tools is well-scoped for a focused site offering an exit-tax calculator and an enquiry submission flow. Each tool serves a clear purpose, and the count feels neither sparse nor bloated.
The calculator side is complete with calculate plus full documentation of inputs, outputs, and assumptions. The enquiry side covers schema discovery, process explanation, and two-step submission, leaving no obvious dead-end for the stated purpose.