Skip to main content
Glama

Map scale distance

bpj_geom_map_scale
Read-onlyIdempotent

Convert a measured map length into ground distance using the scale denominator.

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": {
      "mapCm": "<mapCm>",
      "denominator": "<denominator>"
    },
    "name": "bpj_geom_map_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapCmYes
denominatorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds nothing behavioral beyond that: it does not state the output unit (the same cm as input, or meters), whether the result is rounded, or what large/small values do at the schema's bounds.

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 with no filler or redundant wording. It is arguably under-sized for the ambiguity it leaves, but the sentence itself is clean and efficient.

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?

For a two-parameter, no-output-schema utility the description covers the basic concept, but the output unit and the exact arithmetic relationship are exactly what an agent needs here and are missing. Adequate as a minimum-viable definition, not complete.

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?

Schema description coverage is 0%; only bare titles ('Map length (cm)', 'Scale denominator') and numeric bounds exist. The description merely restates the parameter names and never gives the combining formula or the unit of the returned ground distance, so it fails to compensate for the coverage gap on a 2-parameter tool.

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?

Names a specific verb+resource ('Convert a measured map length into ground distance') plus the mechanism (scale denominator), so the operation is unambiguous. It does not distinguish itself from any sibling, though none of the listed siblings appears to be a competing scale converter, so the gap is minor.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no reference to an alternative tool for related conversions. The agent must infer that this applies to map/plan measurements versus any of the many other geometry tools.

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.