Burs-IA Utils

Distancia elipsoidal (Vincenty)

geo-vincenty

Read-onlyIdempotent

Calcula la distancia geodésica sobre el elipsoide WGS84 (fórmula inversa de Vincenty) con rumbos inicial y final. Cuándo: hay que calcular coordenadas, distancias, rumbos o áreas a partir de puntos dados. No para: calcular la distancia ortodrómica entre dos puntos (geo-haversine). 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 geodesic distance and initial/final bearings between two points on the WGS84 ellipsoid using Vincenty's inverse formula (millimetre accuracy); reports non-convergence for near-antipodal points. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: computing the great-circle distance between two lat/lon points on a spherical Earth (geo-haversine). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

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).
`unit`	No	Distance unit (optional; one of: m, km, mi, nmi, ft; default "m").	m

Output Schema

Name	Required	Description	Default
`unit`	No
`distance`	No
`converged`	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": -37.95103342,
+    "lon": 144.42486789
+  }
+]

addedInput schema / properties / to / examples

Added value: +[
+  {
+    "lat": -37.65282114,
+    "lon": 143.92649554
+  }
+]

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes the geodesic distance and initial/final bearings between two points on the WGS84 ellipsoid using Vincenty's inverse formula (millimetre accuracy); reports non-convergence for near-antipodal points. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: computing the great-circle distance between two lat/lon points on a spherical Earth (geo-haversine). 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."

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description goes well beyond: millimetre accuracy, reporting non-convergence for near-antipodal points, determinism, no network or stored state, and concrete limits (64 KB input, 1 s per call, 1 MB result). These are operational traits the annotations do not convey.

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?

Front-loaded with purpose, then scoped sections for when/not-for/side effects/determinism/limits — easy to scan. Minor waste from the EN text duplicating the inputSchema description verbatim and the bilingual repetition.

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?

An output schema exists so return values need not be explained, and the description still covers the edge case most likely to surprise an agent (non-convergence for near-antipodal points) plus limits and side effects. Nothing needed to call it correctly is 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 nested lat/lon descriptions and the unit enum default documented in the schema, so baseline is 3. The description adds no parameter-level detail beyond that (e.g., it never mentions the unit parameter or the {lat, lon} object shape), so it does not exceed the schema's contribution.

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 (computes geodesic distance and initial/final bearings on the WGS84 ellipsoid via Vincenty's inverse formula) plus accuracy and non-convergence behavior. Explicitly distinguishes itself from the sibling geo-haversine (spherical great-circle distance), so an agent can pick between them without opening schemas.

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

Usage Guidelines5/5

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

Has explicit 'When' (coordinate/distance/bearing/area computations from given points) and 'Not for' (great-circle distance on a spherical Earth — use geo-haversine) sections. The alternative tool is named with the condition that selects it, leaving nothing to inference.

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?