Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

BMI calculator: body mass index and WHO category

calc_bmi
Read-only

Body mass index from weight and height in metric (kg, cm) or imperial (lb, in) units, its WHO adult category (underweight, normal weight, overweight, obesity class I-III) and the weight range that counts as normal for that height. For adults; a screening number, not a diagnosis. Use for health, fitness and nutrition apps. Example: weight=70, height=175. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "weight": "<weight>",
      "height": "<height>"
    },
    "name": "calc_bmi"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNometric (default) or imperial
heightYesHeight in cm (or inches with units=imperial)
weightYesWeight in kg (or lb with units=imperial)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds cost and billing behavior ($0.01/call, first 25 free, failed calls free, repeats not free) and the accuracy limitation (screening, not diagnosis), which no structured field conveys. It stops short of stating output precision or rounding, which would have made it fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The capability, output description and scope are front-loaded before the caveat and pricing, which is the right order. The final pricing sentence is long and somewhat verbose relative to its value, keeping it from a 5.

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?

There is no output schema, so the description carries the return-value burden and does so by naming BMI, the full WHO category ladder and the normal weight range; adult scope, units and cost are also covered. Minor gaps remain on numeric precision and on whether imperial inputs are converted or echoed, but nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns credit by restating the unit semantics ('metric (kg, cm) or imperial (lb, in)') and supplying a concrete example (weight=70, height=175) that implicitly confirms metric defaults and typical magnitudes. It adds modest but real disambiguation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific computation (BMI from weight and height) plus the two derived outputs (WHO adult category and the normal-weight range for that height), so the agent knows exactly what it gets back. The supported unit systems and the adult scope are stated in the first two sentences, distinguishing it from any other calculator sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit context ('use for health, fitness and nutrition apps'), a population restriction ('For adults') and a framing caveat ('a screening number, not a diagnosis'), plus a worked call example. It does not name a when-not condition or point to an alternative, but no sibling overlaps this function, so the guidance is effectively complete.

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.