Burs-IA Utils

Destino desde distancia y rumbo

geo-destination

Read-onlyIdempotent

Calcula el punto de llegada al recorrer una distancia con un rumbo inicial desde un punto. Cuándo: hay que calcular coordenadas, distancias, rumbos o áreas a partir de puntos dados. No para: calcular el rumbo inicial y final (geo-bearing). 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 point reached by travelling a distance along a great circle from a start point on an initial bearing. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: computing the initial and final great-circle bearings (geo-bearing). 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
`from`	Yes	Point as {lat, lon} in decimal degrees (WGS84) (object; required).
`unit`	No	Distance unit (optional; one of: m, km, mi, nmi, ft; default "km").	km
`bearing`	Yes	Bearing in degrees (number; required; min -360; max 360).
`distance`	Yes	Distance (number; required; min 0; max 40000000).

Output Schema

Name	Required	Description	Default
`lat`	No
`lon`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / bearing / examples
```
Added value: +[
+  90
+]
```
- addedInput schema / properties / distance / examples
```
Added value: +[
+  111.195
+]
```
- addedInput schema / properties / from / examples
```
Added value: +[
+  {
+    "lat": 0,
+    "lon": 0
+  }
+]
```
First observedNov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Much of the side-effect sentence restates annotations (read-only, no network, no stored state ≈ readOnlyHint/openWorldHint/destructiveHint), which earns no credit. What is added beyond annotations is substantive: the great-circle (spherical) model, which is the key behavioural difference from an ellipsoidal tool like geo-vincenty, plus hard limits (64 KB input, 1 s per call, 1 MB result). Determinism largely duplicates idempotentHint.

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 purpose is front-loaded and each clause (when / not-for / effects / determinism / limits) is a scannable label. The cost is that the entire block is duplicated verbatim in Spanish and English, roughly doubling length for identical information.

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?

An output schema exists, so return values need no explanation, and the limits and spherical-model note cover the main operational unknowns for a nested-object, 4-parameter tool. Minor gaps remain: nothing on behaviour at extreme bearings or antipodal/polar inputs, and no note that output coordinates are WGS84 decimal degrees.

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 lat/lon ranges, the unit enum and the bearing/distance bounds are already documented in the schema. The description adds only the semantic framing of 'bearing' as an initial bearing along a great circle, and says nothing about unit defaulting or bearing normalisation beyond what the schema shows. 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?

States a specific verb and resource: compute the arrival point after travelling a distance on an initial bearing along a great circle from a start point. That is precise enough to separate it from geo-bearing, geo-midpoint, geo-haversine and geo-vincenty 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?

The 'No para' clause names a concrete alternative (geo-bearing) and the condition that selects it, which is genuinely useful routing. The positive 'Cuándo' clause, however, is over-broad — 'coordinates, distances, bearings or areas... from given points' describes most of the geo-* family, so it does not help an agent choose among geo-haversine, geo-path-length or geo-polygon-area.

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?