Finds the lowest value from a list of numbers to support comparisons, thresholds, or data checks. Use batch_calc for multiple chained operations in one call.
Finds the minimum value from 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 minimum 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 full burden. It correctly implies a pure, side-effect-free computation, but does not disclose edge-case behavior (empty array, NaN, tie handling) that an agent might need to reason about.
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 sentences, front-loaded with the core purpose and followed immediately by the routing hint. No filler or repetition.
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 single-parameter scalar reducer with a fully documented schema and an obvious return value, the description covers what an agent needs. The lack of edge-case notes is a minor gap rather than a blocking one.
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 documented in the schema itself. The description adds no syntax or format detail beyond what the schema provides, 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 ('Finds the minimum value from a list of numbers'), which is unambiguous and self-differentiating from the sibling 'max'. An agent can select this tool without reading the 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 the alternative (batch_calc) and the condition that selects it ('several operations or chained steps in one call'), which is genuine routing guidance. It stops short of stating when-not to use min, but for a single-value reducer that is largely self-evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.