Skip to main content
Glama

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

Point at a bearing and distance

destination_point
Read-onlyIdempotent

Where do you end up going a given distance on a given bearing from a start point? The end point on the WGS84 ellipsoid, in the formats you ask for. 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>",
      "bearing": "<bearing>",
      "distance": "<distance>"
    },
    "name": "destination_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOutput formats for the end point (default dd,dms).
refNoReference point for short plus codes (in the input, and to add a short code to the output), like "40.4,-79.9".
fromYesStart, any format.
unitNom (default), km, mi, nmi or ft.
orderNoFor letterless numbers: latlon (default) or lonlat. Hemisphere letters and lat/lon labels win.
bearingYesInitial bearing in degrees from true north (-360 to 360).
distanceYesDistance (up to 40,075 km).
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.1/5.0
Behavior3/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 the useful detail that results are computed on the WGS84 ellipsoid and returned in requested formats, but says nothing about precision, edge cases, or error behavior.

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 core sentence is reasonably front-loaded, but the question format is indirect and the trailing promotional URL for 'More APIs from FitzTopPicks' is pure noise that does not help an agent invoke the tool.

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?

For an 8-parameter tool with no output schema, the description covers the core computation and the ellipsoid model, and annotations cover safety. However, it does not describe the shape of the returned end point or how multiple output formats are combined, leaving a modest gap.

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 parameter is already documented in the schema, including enums for unit, order and inputFormat. The description only adds the vague phrase 'in the formats you ask for', which does not meaningfully extend the schema, so the baseline 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 states a specific computation: the end point reached from a start point at a given bearing and distance, on the WGS84 ellipsoid. That is a clear verb+resource, though it is phrased as a rhetorical question and does not distinguish itself from siblings like distance_between_points or great_circle_path.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The agent must infer from the question phrasing that this is the forward geodesic problem, with no routing away from related coordinate or distance tools.

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