John's Essentials

convert_geo

GPS & Map Converter — Convert between GPX, KML, KMZ and GeoJSON — the GPS-track and mapping formats used by Garmin, Strava, Google Earth and every GIS tool. Track segments, per-point timestamps, elevations and polygon holes all survive the trip. Anything that cannot survive (a polygon becoming a GPX track, an unlocated feature) is reported in the X-Conversion-Notes header rather than dropped quietly; pass strict=true to refuse instead. [category: convert]

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Must differ from the detected source — gpx→gpx is a 400; format-version upgrades happen implicitly on read.
`file`	Yes	A .gpx, .kml, .kmz or .geojson file.
`from`	No	Optional. Detected from content; declare it only when the upload has no meaningful filename.
`strict`	No	Stop the conversion rather than hand back a file that has lost something. Off by default: you get the result plus a note about anything that could not be carried over.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026
- addedInput schema / properties / from / x-ui
```
Added value: +{
+  "unset_label": "Read from file"
+}
```

Changed4 schema fields changedSep 11, 2026

addedInput schema / properties / strict / default
```
Added value: +false
```

changedInput schema / properties / strict / description

Previous value: -"When true, refuse the conversion instead of returning a result that loses information."New value: +"Stop the conversion rather than hand back a file that has lost something. Off by default: you get the result plus a note about anything that could not be carried over."

removedInput schema / properties / strict / enum
```
Removed value: -[
-  "true",
-  "false"
-]
```

changedInput schema / properties / strict / type

Previous value: -"string"New value: +"boolean"

First observedSep 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations, the description discloses the lossy-conversion policy: anything that cannot survive is reported in the X-Conversion-Notes header rather than dropped silently, and strict=true switches to refusal. It also promises preservation of track segments, timestamps, elevations, and polygon holes, giving the agent a clear behavioral model. This does not contradict the annotations.

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?

The description is compact, front-loaded with purpose, then fidelity guarantees, then failure behavior and the strict option. Each clause earns its place, and the [category: convert] tag adds useful discoverability without clutter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a conversion tool with full parameter schema coverage, the description covers the supported formats, what is preserved, how loss is communicated, and how to make loss fatal via strict. Agents have enough context to select and invoke the tool correctly; an output schema is not needed because the output type is obviously a converted file.

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 the schema already documents file, to, from, and strict with enums, defaults, and conditional rules. The description adds valuable domain context but no new parameter-level semantics, so the baseline 3 is appropriate.

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 names a specific verb ('Convert') and a precise resource domain ('between GPX, KML, KMZ and GeoJSON'), immediately distinguishing it from generic siblings like convert_file or convert_document. The opening 'GPS & Map Converter' plus the explicit format list leaves no ambiguity about scope.

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?

It clearly establishes the intended context: GPS-track and mapping formats used by Garmin, Strava, Google Earth, and GIS tools. It also explains when data survives conversion and when strict mode is appropriate. However, it never explicitly names alternative tools or states when not to use this tool, so it stops short of full 5-level guidance.

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

All John's Essentials tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?