Skip to main content
Glama

MapMap

by ai.mapmap
OverviewDiscussionsAdmin

geo_bearing

Initial bearing from one coordinate to another, in degrees clockwise from true north (0-360). This is the bearing at the START of the geodesic; over long distances the bearing changes en route. Local computation: no network call, no quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesEnd coordinate.
fromYesStart coordinate.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bearing_degYesInitial bearing from `from` to `to`, degrees clockwise from true north, normalised to 0–360. Note this is the bearing at the start of the geodesic: over long distances the bearing changes en route.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $defs / LatLon / anyOf
      Added value: +[
+  {
+    "properties": {
+      "lat": {
+        "description": "Latitude in decimal degrees (−90 to 90).",
+        "format": "double",
+        "type": "number"
+      },
+      "lon": {
+        "description": "Longitude in decimal degrees (−180 to 180).",
+        "format": "double",
+        "type": "number"
+      }
+    },
+    "required": [
+      "lat",
+      "lon"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "GeoJSON position [lon, lat]: longitude FIRST.",
+    "items": {
+      "format": "double",
+      "type": "number"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  }
+]
    • changedInput schema / $defs / LatLon / description
      Previous value: -"A WGS84 coordinate pair in decimal degrees."New value: +"A WGS84 coordinate in decimal degrees: a {lat, lon} object (preferred), or a GeoJSON [lon, lat] array with LONGITUDE FIRST, the same order as every polygon field on this server."
    • removedInput schema / $defs / LatLon / properties
      Removed value: -{
-  "lat": {
-    "description": "Latitude in decimal degrees (−90 to 90).",
-    "format": "double",
-    "type": "number"
-  },
-  "lon": {
-    "description": "Longitude in decimal degrees (−180 to 180).",
-    "format": "double",
-    "type": "number"
-  }
-}
    • removedInput schema / $defs / LatLon / required
      Removed value: -[
-  "lat",
-  "lon"
-]
    • removedInput schema / $defs / LatLon / type
      Removed value: -"object"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses three important traits: the result is the initial bearing (not final), the bearing changes en route for long distances, and the operation is local with no network or quota implications. It does not describe error behavior or what happens with invalid coordinates, but for a pure geometry calculation this is a minor gap. No contradiction with annotations exists.

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?

Two sentences with zero filler. The first sentence states the result and unit; the second adds the geodesic nuance and the local-computation performance trait. Each sentence earns its place, and the most important information is front-loaded.

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?

The tool is a simple geometry computation with a rich input schema and an output schema. The description covers the essential behavioral context (initial bearing, change along the geodesic, local computation) and does not need to explain return values because an output schema exists. An agent reading this description has everything necessary to invoke the tool correctly and interpret the result in context.

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%. The 'from' and 'to' parameters are clearly named and described as 'Start coordinate' and 'End coordinate,' and the shared LatLon definition explains both object and array forms, including the 'longitude FIRST' order. The tool description itself adds no parameter-level semantics, so it neither improves nor harms the schema's already sufficient documentation. The baseline 3 applies.

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 highly specific operation and output: 'Initial bearing from one coordinate to another, in degrees clockwise from true north (0-360).' It also clarifies the geodesic context ('bearing at the START of the geodesic'), which distinguishes this from an average or final bearing. None of the sibling tools compute bearing, so there is no ambiguity.

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?

The description gives clear contextual guidance: the bearing is the initial one and changes over long distances, implying that for navigation along a route one should not assume a constant bearing. It also notes 'Local computation: no network call, no quota,' which helps an agent decide when a cheap local calculation suffices. However, it does not explicitly name alternative tools (e.g., geo_destination or geo_distance) or state exclusion conditions, so it falls short of a 5.

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

All MapMap toolsInspect
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