Calculate BMI using weight (kg) and height (cm) to receive WHO and Asian-Pacific categories plus a healthy weight range.
BMI from weight(kg) and height(cm). Returns WHO and Asian-Pacific categories with healthy weight range.
| Name | Required | Description | Default |
|---|---|---|---|
| heightCm | Yes | ||
| weightKg | Yes |
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 must disclose behavior. It mentions the return value categories and healthy weight range, but does not explicitly state that it is a pure, non-destructive calculation or describe error handling. This is acceptable for a calculator but lacks depth.
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, well-structured sentence with no redundancy. It front-loads the core formula and states the output, every word earning its place.
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 simple two-parameter calculator with no output schema, the description covers the essentials: inputs with units, the calculation, and the return categories. It could explicitly state that the numeric BMI value is also returned and any input validation rules, but it is largely complete.
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 0%, so the description must compensate. It clarifies units (kg and cm), which adds value, but does not provide constraints, expected ranges, or further parameter detail beyond what the parameter names already suggest.
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 states that the tool computes BMI from weight (kg) and height (cm) and mentions the output (WHO and Asian-Pacific categories, healthy weight range). This distinguishes it from sibling calculators like bmr_calculator or tdee_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?
The description implies use for BMI calculation but does not explicitly name alternatives or provide when-to-use/when-not-to-use guidance. For a simple calculator, this is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.