Calculates the median of a list of numbers. Use batch_calc for multiple or chained operations in one call.
Calculates the median of a list of numbers. For several operations or chained steps in one call, use batch_calc.
| Name | Required | Description | Default |
|---|---|---|---|
| numbers | Yes | Array of numbers to find the median of |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden; it says nothing about behavior for an empty array, even-length input (averaging the two middle values), or non-numeric entries. For a deterministic pure-math function the risk is low, but the caller is left to infer edge-case handling.
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?
Two tight sentences: the core operation first, then the routing hint. No filler, no repetition of the tool name, and the most important information leads.
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?
With one simple parameter, no output schema, and no annotations, the definition gives an agent enough to invoke correctly. The only omission is edge-case return behavior, which is minor for this tool class.
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?
Schema description coverage is 100% and the single parameter is fully documented as "Array of numbers to find the median of," including minItems=1. The description adds no format or constraint detail beyond the schema, so the baseline of 3 applies.
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?
States a specific verb and resource ("Calculates the median of a list of numbers"), which cleanly separates it from sibling statistics tools such as mean, mode, min, and max without needing to open any schema.
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?
Names an explicit alternative and the condition that selects it: chained or multi-step operations should go to batch_calc. It does not, however, cover when to prefer median over mean/mode for a given problem, so it falls short of full when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.