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 full burden. It describes the calculator's behavior but does not disclose the tool's own output format (e.g., plain text, JSON) or that it is a read-only operation. The tool's side effects and return structure are unmentioned.
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 front-loads the purpose and enumerates the covered topics (inputs, outputs, assumptions, tables). Every word contributes to the meaning without redundancy.
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 no-parameter describe tool with no output schema, the description is largely complete: it tells the agent what the tool does. The only missing detail is the return format, but given the trivial nature of the tool, this is a minor gap. Annotations could have added safety hints but are absent.
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 input schema has zero parameters, and schema description coverage is 100% (trivially). The description does not need to add parameter details since none exist. The baseline for 0 parameters is 4, and the description adds no extra meaning beyond the empty schema.
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 explicitly states that the tool describes the calculator's inputs, outputs, assumptions, and tables. It clearly identifies the resource (Driver capacity planner calculator) and the verb (describe) is implied by the name and context. It distinguishes from siblings like 'calculate' and 'enquiry_describe' by naming the specific calculator.
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?
No explicit guidance is given on when to use this tool versus alternatives such as 'calculate' or 'enquiry_describe'. The usage is implied by the name, but the description does not state exclusions or conditions for choosing this tool over others.
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 clearly distinct role: running the calculator, describing the calculator, explaining the enquiry process, listing enquiry fields, and submitting an enquiry. There is no meaningful overlap or ambiguity between them.
Names are readable and mostly memorable, but they mix verb-first forms like calculate and submit_enquiry with noun-first forms like calculator_describe and enquiry_describe. The pattern is not fully consistent, though it is still understandable.
Five tools is a lean but well-scoped set for the site's purpose: calculator execution, calculator documentation, enquiry explanation, enquiry schema, and enquiry submission. Each tool earns its place without redundancy.
The tool surface covers the full user journey for both calculator usage and the two-step enquiry submission, including field discovery and consent handling. No obvious gaps or dead ends are visible for the stated domain.