Skip to main content
Glama

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

Convert a coordinate between formats

convert_coordinates
Read-onlyIdempotent

Convert a location between decimal degrees, degrees-minutes-seconds, UTM, UPS, MGRS, Plus Codes, geohash and Maidenhead (input format detected). Use for "what is 40°26'46"N 79°58'56"W in MGRS" or "UTM of 51.5, -0.12". More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_coordinates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoComma-separated outputs (default all): dd, dms, ddm, utm, mgrs, pluscode, geohash, maidenhead.
latNoLatitude in decimal degrees (instead of input).
lonNoLongitude in decimal degrees (instead of input).
refNoReference point for short plus codes (in the input, and to add a short code to the output), like "40.4,-79.9".
inputNoThe coordinate as text, up to 200 characters, URL-encoded.
orderNoFor letterless numbers: latlon (default) or lonlat. Hemisphere letters and lat/lon labels win.
utmZoneNoForce a UTM zone (1-60) instead of the standard one (80°S-84°N only).
ddDecimalsNoDecimal places for decimal degrees, 0-10 (default 6).
ddmDecimalsNoDecimal places on DDM minutes, 0-6 (default 4).
dmsDecimalsNoDecimal places on DMS seconds, 0-4 (default 1).
inputFormatNoSkip auto-detection: latlon (dd/dms/ddm), utm, ups, mgrs, pluscode, geohash, maidenhead.
geohashLengthNoGeohash characters, 1-12 (default 9, about 5 m).
mgrsPrecisionNoMGRS square size in metres: 1 (default), 10, 100, 1000, 10000, 100000.
pluscodeLengthNoPlus code digits: 2, 4, 6, 8, 10 (default) to 15.
maidenheadLengthNoMaidenhead characters: 2, 4, 6 (default) or 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/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 the safety profile is covered. The description adds genuinely new operational behavior: the input format is auto-detected, so the agent knows it can pass raw coordinate text without prescribing the format first. It does not say that multiple formats are returned by default, which is left to the schema.

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 and two example invocations are front-loaded in two tight sentences. The trailing marketing URL for "more APIs from FitzTopPicks" is promotional filler that does not help an agent invoke the tool and dilutes an otherwise lean description.

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?

This is a complex tool with 15 optional parameters and no output schema, so the description could reasonably note that output is a set of format conversions (default all) and that at least one of input or lat/lon must be supplied. The schema compensates fully, but the description itself leaves these invocation-critical points unstated.

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%, so every one of the 15 parameters is documented with bounds, defaults and enum values in the schema itself. The description only names the format families and the auto-detection behavior, adding essentially no parameter-level detail beyond that, which is the expected baseline here.

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?

States a specific verb and resource (convert a location) plus the full set of supported format families, which lets an agent distinguish this from siblings like coordinate_formats or identify_coordinate purely on the text.

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

Usage Guidelines4/5

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

Two concrete example queries ("what is 40°26'46"N 79°58'56"W in MGRS", "UTM of 51.5, -0.12") give clear context for when to reach for this tool, and "input format detected" signals the input may be free text. It stops short of naming when not to use it or which sibling to prefer for format listing or extraction.

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