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?
There are no annotations, so the description carries the burden of behavioral disclosure. It does explain what content the tool returns (inputs, outputs, assumptions, tables), but it does not state whether the operation is read-only, what the output format is, or that no calculation is performed.
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, focused sentence that efficiently conveys the scope of the tool. It wastes no words and is easy to parse.
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 zero-parameter descriptive tool, the description sufficiently outlines the content coverage: inputs, outputs, assumptions, and tables. It could be slightly more complete by explicitly noting its relationship to the 'calculate' sibling, but no critical invocation information is missing.
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, so the baseline is 4. The description adds useful context by indicating that the calculator's inputs have units, ranges, and defaults, even though it does not enumerate them. No invocation parameters are needed, so no additional parameter semantics are required.
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 conveys that this tool provides information about the calculator's inputs, outputs, assumptions, and tables, which distinguishes it from the sibling 'calculate' tool. However, it lacks an explicit verb like 'returns' or 'describes', so the purpose is implied rather than directly stated.
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 guidance is given about when to use this tool instead of siblings such as 'calculate' or 'enquiry_describe'. The agent must infer from the name and title that this is a descriptive utility rather than a computation tool.
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 purpose: calculate runs the calculator, calculator_describe explains the calculator, enquiry_describe explains the enquiry flow, enquiry_fields provides the schema, and submit_enquiry submits. There is no meaningful overlap or ambiguity between them.
The names are readable but follow mixed conventions: 'calculate' is a bare verb, while 'calculator_describe' and 'enquiry_describe' use noun_verb reversed, and 'enquiry_fields' is a noun phrase. The pattern is not chaotic, but it is inconsistent enough to be noticeable.
Five tools is well-scoped for a calculator-plus-enquiry server. Each tool covers a necessary function without bloat or redundancy.
The toolset fully covers its stated domain: calculating costs, understanding the calculator, understanding the enquiry process, fetching the enquiry fields, and submitting an enquiry. There are no obvious dead ends or missing operations.