Burs-IA Utils

Punto medio geográfico

geo-midpoint

Read-onlyIdempotent

Calcula el punto medio sobre el círculo máximo entre dos puntos, o centro geográfico de varios puntos. 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 midpoint along the great circle between two points, or the geographic center (mean of 3-D vectors) of up to 10,000 points. 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
`points`	Yes	Points (array of object; required; at least 1 items).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / points / examples

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

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so the description earns credit mainly for adding hard limits (64 KB JSON input, 1 s per call, 1 MB result), determinism and no-network/no-stored-state guarantees. Those operational limits are genuinely useful and not derivable from the annotations.

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 structured What/When/Not-for/Effects/Deterministic/Limits layout is front-loaded and scannable. The only cost is that the entire block is duplicated in Spanish and English, which roughly doubles length for the same information.

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?

With an output schema present, return values need no explanation, and the description covers the remaining risks: which mode applies based on point count, limits, and determinism. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real semantics the schema cannot express: the number of points changes behavior (two points = great-circle midpoint, several points = mean 3-D vector center). It still does not describe the {lat, lon} object shape in prose, but the schema and its examples do that well.

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?

Names a specific verb and resource ('computes the midpoint along the great circle between two points, or the geographic center of ... up to 10,000 points') and thereby distinguishes itself from the many geo-* siblings. An agent can tell it apart from geo-haversine, geo-destination and geo-bearing 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?

It gives an explicit 'Not for' clause naming the sibling geo-destination and the exact scenario (origin + distance + bearing), which is strong routing guidance. The 'When' clause is clear in context but slightly loose — it mentions computing distances, bearings and areas, which this tool does not actually return, so the positive trigger is fuzzier than the negative one.

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?