Burs-IA Utils

Rumbo entre dos puntos

geo-bearing

Read-onlyIdempotent

Calcula el rumbo inicial y final (grados desde el norte) entre dos puntos, con etiqueta de brújula. Cuándo: hay que calcular coordenadas, distancias, rumbos o áreas a partir de puntos dados. No para: calcular el punto de llegada desde un origen, una distancia y un rumbo (geo-destination). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Computes the initial and final great-circle bearings (degrees clockwise from true north) from one point to another, with 16-point compass labels. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: computing the point reached from a start, distance and bearing (geo-destination). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

Input Schema

Name	Required	Description	Default
`to`	Yes	Point as {lat, lon} in decimal degrees (WGS84) (object; required).
`from`	Yes	Point as {lat, lon} in decimal degrees (WGS84) (object; required).

Output Schema

Name	Required	Description	Default
`compass`	No
`final_bearing`	No
`initial_bearing`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / from / examples

Added value: +[
+  {
+    "lat": 51.5074,
+    "lon": -0.1278
+  }
+]

addedInput schema / properties / to / examples

Added value: +[
+  {
+    "lat": 48.8566,
+    "lon": 2.3522
+  }
+]

First observedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld=false and non-destructive, so the 'Sin efectos secundarios / solo lectura' sentence largely just restates them. However, the definition adds real information that the annotations do not: determinism (same input, same output) and hard operational limits (64 KB JSON input, 1 s per call, 1 MB result), which matter for an agent that plans calls and batches inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The definition is front-loaded with the core definition, which is followed by the When, Not-for, side-effects, determinism and limits facts; each piece of information is tagged, so an agent can locate any of them quickly. The main efficiency cost is that the whole block is written in parallel Spanish and English, roughly doubling length, and the side-effects sentence duplicates the annotations.

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 definition already includes what an agent needs in order to call this tool correctly: ordered endpoints, units (degrees clockwise from true north), and platform limits. An output schema exists and describes the return shape, so the definition's brief note on compass labels is sufficient rather than missing. No prerequisites, for example a coordinate format or WGS84 requirement, are undocumented.

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%: both the 'from' and 'to' objects, their nested lat/lon fields and WGS84 ranges are fully documented with examples, so the schema does the heavy lifting. The description adds only that the two inputs are ordered endpoints ('from one point to another'), which is mild added value. The correct baseline is 3 when the schema is complete.

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 definition states a precise verb and resource ('Calculates the initial and final bearings... between two points') and adds the concrete output form (degrees clockwise from true north, 16-point compass labels). A key fact is that it explicitly names the sibling tool this is not meant to replace (geo-destination), so an agent can distinguish its purpose without opening a 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 contains an explicit "Not for" clause that names geo-destination and the exact scenario that selects it (computing the arrival point from an origin, distance and bearing), which is strong routing guidance. The positive "When" clause is broader and family-level ('coordinates, distances, bearings or areas'), so it overlaps with several geo siblings (geo-haversine, geo-midpoint, geo-polygon-area), leaving this half of the routing less precise.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?