Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Check a coordinate and name its format

identify_coordinate
Read-onlyIdempotent

Is this text a valid coordinate, and in which format (MGRS, UTM, Plus Code, Maidenhead...)? Gives the normalized form and the point. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "input": "<input>"
    },
    "name": "identify_coordinate"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoReference point for short plus codes (in the input, and to add a short code to the output), like "40.4,-79.9".
inputYesThe coordinate text.
orderNoFor letterless numbers: latlon (default) or lonlat. Hemisphere letters and lat/lon labels win.
inputFormatNoSkip auto-detection: latlon (dd/dms/ddm), utm, ups, mgrs, pluscode, geohash, maidenhead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the return content (normalized form plus the point), which matters since there is no output schema, but it says nothing about behavior on invalid input or how lenient the parsing is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are front-loaded and efficient: purpose, formats, and return value. The trailing promotional line about 'More APIs from FitzTopPicks' with UTM parameters does not help an agent select or invoke the tool and dilutes the definition.

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 no output schema, the description rightly covers the return shape at a high level, and the format examples set expectations. It falls short on error/validation behavior, which is central to a tool whose first question is 'is this valid', and on how the optional ref and inputFormat overrides interact.

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 enums (order, inputFormat) are documented in-schema with their fallback semantics. The description mentions the recognizable formats but adds no syntax or precedence detail beyond what the schema already provides, so the baseline of 3 applies.

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-plus-resource: validate a text string as a coordinate and identify its format, naming concrete formats (MGRS, UTM, Plus Code, Maidenhead) and stating it returns the normalized form and the point. It is clear what the tool does, but it never distinguishes itself from plausible siblings such as convert_coordinates or coordinate_formats, leaving the agent to infer the boundary.

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 rather than stated: the question phrasing ('Is this text a valid coordinate, and in which format...') signals this is an identification/validation tool rather than a converter, which helps. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative for converting coordinates between formats.

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