Skip to main content
Glama

Compare two heights

compare_heights
Read-onlyIdempotent

Calculate the absolute difference and A-to-B ratio, and create an editable, true-scale HeightPair comparison link.

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_a": "<height_a>",
      "height_b": "<height_b>"
    },
    "name": "compare_heights"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoside
unitsNometric
name_aNoPerson A
name_bNoPerson B
height_aYesA height such as 170 cm, 1.85 m or 5 ft 11 in. Bare numbers follow the selected input units.
height_bYesA 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

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by disclosing what is produced: a numeric difference, a ratio, and an editable, true-scale comparison link. It stops short of saying whether the link is returned as a URL string or persisted, which is a minor ambiguity.

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?

A single front-loaded sentence covering both computational outputs and the generated artifact, with no filler. Density is good, though 'HeightPair comparison link' is a product term the reader must already know.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and low schema description coverage, the definition should at least characterize the response shape and how mode/units alter results. It gestures at the return values but leaves the mechanics of the link and parameter effects underspecified.

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

Parameters2/5

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

Only height_a and height_b carry schema descriptions (33% coverage); mode, units, name_a and name_b are undocumented beyond enum values and defaults. The description says nothing about any of the six parameters, not even that units drive interpretation of the two required heights, so it fails to compensate for the coverage gap.

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 names specific operations on a specific resource: computing an absolute difference and an A-to-B ratio, plus generating a comparison link. It is clearly distinct from convert_height and height_percentile, though it never names those siblings to reinforce the distinction.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (two valid heights, unit selection), and no routing away from convert_height for single-height conversions. The agent must infer the use case entirely from the purpose statement.

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