Skip to main content
Glama

Flat map against the sphere

compare_flat_map_distance
Read-onlyIdempotent

Compares the distance between two cities on a north-polar flat-Earth map with their great-circle distance over a sphere. Returns both distances and the factor by which the map stretches or shrinks the pair.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "compare_flat_map_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSecond city, one of the website's 20 cities: Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singapore, Sydney or Tokyo.
fromYesFirst city, one of the website's 20 cities: Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singapore, Sydney or Tokyo.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavior is fully covered elsewhere. The description's added value is modest but real: it discloses the north-polar projection and that both distances plus a stretch/shrink factor are returned. It does not mention the 20-city restriction (left to the schema) or any computation caveats.

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?

Two sentences, zero filler, with the comparison (the core action) front-loaded and the return contents following. Nothing redundant given the structured fields.

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?

An output schema exists so return values need not be explained, and the schema fully documents parameters; annotations cover safety. The only shortfall is the absence of routing guidance against the distance-related siblings, which keeps it just short of complete.

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 description coverage is 100% and both parameters enumerate the exact allowed city list, so the schema carries the full burden. The description only says 'two cities' and adds no format, ordering, or symmetric/ordered semantics beyond what the schema provides — baseline 3.

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?

The description states a precise verb and resource — comparing two cities' flat-map distance against their great-circle distance — and names the specific projection (north-polar flat-Earth). An agent can immediately distinguish this from get_flight_distance or compare_true_size without opening a schema.

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 implied by the purpose: reach for this when you want to demonstrate map distortion rather than an actual travel distance. However, there is no explicit 'use this instead of X when Y' statement and no exclusions, so the agent must infer the selection criteria relative to siblings like get_flight_distance.

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.