Skip to main content
Glama

Get calculator inputs

get_calculator
Read-only

Describes a calculator's inputs: key, label, kind, unit, allowed options, limits and default value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCalculator slug from search_calculators.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a safe, closed read (readOnlyHint=true, openWorldHint=false), so the description's burden is lighter. It adds genuine value by disclosing the shape of the returned data — key, label, kind, unit, allowed options, limits, default — which is important because no output schema exists. It does not say whether the call fails for an unknown slug, which is the remaining gap.

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 sentence with a colon-delimited list of returned fields, front-loaded with the verb and resource. Every element earns its place and there is no filler or 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?

For a one-parameter read tool with no output schema, the description covers both what it does and what it returns, which is the bulk of what an agent needs. It is missing only invocation guidance relative to run_calculator and error behavior for a bad slug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter and schema description coverage is 100%, with the schema already explaining that slug is a calculator slug from search_calculators. The description's field list describes the response, not the parameter, so it adds no meaning about slug format or behavior. Baseline 3 applies.

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 states a specific resource and verb: it returns the input-parameter metadata for one calculator, enumerated as key, label, kind, unit, options, limits and default. An agent can tell this is a schema-introspection tool rather than an execution tool. It stops short of naming how it differs from run_calculator or list_calculators, so it is clear but not sibling-differentiated.

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 must infer that this is the step to take before run_calculator to learn what inputs are required. The workflow hint that the slug comes from search_calculators lives in the parameter schema, not the description. There is no explicit when-to-use, when-not-to-use, or alternative named.

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