Skip to main content
Glama

gridref_to_latlon

Convert Ordnance Survey grid references to WGS84 latitude and longitude, choosing the square centre or southwest corner for accurate mapping.

Instructions

Convert an OS grid reference to WGS84 latitude/longitude.

Args: grid_ref: e.g. "SU 123 456", "NN166712", "TQ3080" or numeric "412300,145600". centre: return the centre of the referenced square (True) or its SW corner (False).

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": {
      "grid_ref": "<grid_ref>"
    },
    "name": "gridref_to_latlon"
  }
}

Input Schema

NameRequiredDescriptionDefault
centreNo
grid_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden alone. It usefully discloses the meaningful behavioral choice behind `centre` (centre of the referenced square vs. its SW corner), which is real semantic behavior, but it says nothing about the return value shape, coordinate precision, or what happens for an invalid/ambiguous grid reference.

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 core purpose is front-loaded in one sentence and the parameter block is compact with concrete examples rather than abstract prose. The Python-docstring 'Args:' formatting is slightly stylized but every line carries information; no filler.

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 simple two-parameter conversion tool with no output schema, the input side is well covered but the return side is not described at all — the agent cannot tell whether it receives a tuple, string, or object, nor the precision of the result. That gap matters precisely because there is no output schema to fall back on.

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 description coverage is 0%, so the description must compensate, and it does: it lists four concrete accepted `grid_ref` formats (spaced, compact, short, numeric comma-separated) and explains both branches of the `centre` boolean. Neither parameter is left ambiguous, though error/parsing edge cases are not addressed.

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 first sentence states a precise verb ('Convert') and both the source and target coordinate systems ('OS grid reference to WGS84 latitude/longitude'). The direction of conversion inherently distinguishes it from the sibling latlon_to_gridref, so an agent can select it without opening the schema.

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 explicit when-to-use guidance, no mention of the inverse tool (latlon_to_gridref) as an alternative, and no statement of preconditions or limits. The use case is only implied by the conversion direction, leaving the agent to infer selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.