Skip to main content
Glama

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

A circle of a radius around a point

geodesic_circle
Read-onlyIdempotent

A true circle of a given radius around a point as a GeoJSON polygon (correct on the ellipsoid, across the antimeridian). Use for "everything within 50 km of" map shapes. 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": {
      "center": "<center>",
      "radius": "<radius>"
    },
    "name": "geodesic_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoReference point for short plus codes in the input, like "40.4,-79.9".
unitNoUnit of the distances you send: m, km (default), mi, nmi, ft.
orderNoFor letterless numbers: latlon (default) or lonlat.
centerYesThe centre, any format.
formatNojson (default: the answer with a "geojson" Feature) or geojson (the Feature alone, Content-Type application/geo+json, ready for a map).
pointsNoVertices, 8-720 (default 64).
radiusYesRadius in "unit" (more than 0, up to 10000 km).
decimalsNoDecimal places on coordinates, 4-9 (default 7, about 1 cm).
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely behavioral facts beyond that: the result is geometrically correct on the ellipsoid and handled across the antimeridian, which affects whether the output can be trusted near ±180°. It doesn't discuss the json-vs-geojson return envelope, but that is documented in 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.

Conciseness3/5

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

The technical content is two tight sentences with the output format front-loaded. The trailing 'More APIs from FitzTopPicks' promotional line with UTM parameters is pure noise that doesn't help an agent select or invoke the tool.

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 10-parameter geometry generator with no output schema, the description covers the essential unknowns: what is returned (a GeoJSON polygon), and the two correctness caveats (ellipsoid, antimeridian) an agent could otherwise get wrong. Everything else — units, vertex count, decimals, input format — is fully documented in the schema, so only a note on the return envelope is arguably missing.

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%, with per-parameter docs for center, radius, unit, points, decimals, antimeridian and format, so the baseline is 3. The description only restates that a radius is required and the output is a polygon; it adds no syntax, defaults or format guidance beyond the schema.

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 gives a specific verb+resource: it produces 'a true circle of a given radius around a point as a GeoJSON polygon'. It also names the defining properties (ellipsoid-correct, antimeridian-aware), which separates it from a point-to-point tool like distance_between_points or great_circle_path without opening any schema.

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 supplies a concrete use scenario: '"everything within 50 km of" map shapes', which tells the agent the situation this tool is for. It stops short of naming alternatives (e.g. when a path or a destination point is the right call) or stating exclusions, so it's clear context without routing rules.

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