Skip to main content
Glama

Convert a height

convert_height
Read-onlyIdempotent

Convert cm, meters, feet and inches using the exact 25.4 mm inch definition.

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

Input Schema

NameRequiredDescriptionDefault
unitsNometric
heightYesA height such as 170 cm, 1.85 m or 5 ft 11 in. Bare numbers follow the selected input units.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The description adds one genuinely useful behavioral claim — the exact 25.4 mm inch definition, i.e. conversion precision — but says nothing about return format, rounding, or whether both unit systems are returned.

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?

One sentence, front-loaded with the conversion scope and the precision convention, with zero filler. Nothing could be removed without losing information.

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 two-parameter, stateless conversion utility with no output schema and full annotation coverage, the definition supplies enough to call it correctly. The only meaningful gap is that the output shape and rounding behavior are unstated, which matters modestly for a precision-oriented conversion tool.

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?

Schema coverage is 50%: 'height' is documented in the schema (including the note that bare numbers follow the selected input units), while 'units' has only an enum [metric, imperial] and a default with no description. The description partly compensates by naming the accepted unit spellings (cm, m, ft, in), but it never explains what the 'units' switch actually controls.

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 gives a specific verb (convert) and resource (heights in cm, meters, feet, inches), which lets an agent distinguish it from siblings like compare_heights or height_percentile without opening the schema. It stops short of stating the direction/shape of the conversion output, so it is clear but not fully specified.

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: the domain (unit conversion of a height) is evident, but there is no explicit when-to-use or when-not-to-use statement, and no routing to compare_heights or height_percentile. An agent can infer the case but must do the reasoning itself.

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