Skip to main content
Glama

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

Great-circle route waypoints

great_circle_path
Read-onlyIdempotent

Waypoints along the shortest route between two points on the Earth (geodesic), as GeoJSON, by step distance or number of points. Use for flight-path lines on a map. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "great_circle_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd, any format.
refNoReference point for short plus codes in the input, like "40.4,-79.9".
fromYesStart, any format: "40.6413,-73.7781", "18TWL8613...", a plus code...
stepNoDistance between points, in "unit" (send step or points).
unitNoUnit of the distances you send: m, km (default), mi, nmi, ft.
orderNoFor letterless numbers: latlon (default) or lonlat.
formatNojson (default: the answer with a "geojson" Feature) or geojson (the Feature alone, Content-Type application/geo+json, ready for a map).
pointsNoHow many points, 2-2000 (default 100 when step is not sent).
decimalsNoDecimal places on coordinates, 4-9 (default 7, about 1 cm).
waypointsNoAdd the list of points with distance and bearing (default false).
inputFormatNoSkip auto-detection of the input format.
antimeridianNosplit (default, RFC 7946: cut at ±180° into a Multi- geometry, crossing points solved exactly) or unwrap (one geometry with longitudes past ±180°, for web maps that pan across the date line).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds little beyond that — nothing about the 2000-point cap, the 100-point default, precision limits, or how the antimeridian split changes the returned geometry — and the remaining sentence is promotional rather than behavioral.

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 earn their place, but the closing sentence is a marketing link with UTM tracking that carries zero value for tool selection or invocation and dilutes the definition.

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?

For a read-only geometry generator with a fully documented 12-parameter schema and no output schema, the description covers purpose, output shape, and the step/points sizing choice well. Return-value details like the optional waypoint list with distance and bearing are left entirely to the schema, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% but the description still adds real meaning: it explains that sizing is either step distance or number of points (a mutually exclusive choice the schema only hints at) and that the output is a GeoJSON geometry suitable for map rendering. It complements rather than repeats the parameter docs.

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 and resource — waypoints along the shortest (geodesic) route between two points, returned as GeoJSON — and the step-vs-points sizing model. That is enough to separate it from siblings like distance_between_points, destination_point, and geodesic_circle.

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?

It gives one concrete use case ("flight-path lines on a map"), which implies context, but never states when not to use it or which sibling to pick instead (e.g., distance_between_points for a bare distance, destination_point for a single bearing/offset). Guidance is implied rather than explicit.

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