Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Coordenadas GMS a decimales

coordinates-to-decimal
Read-onlyIdempotent

Convierte coordenadas en GMS (4°38'8"N), grados y minutos decimales o decimales con hemisferio (N/S/E/W/O) a grados decimales. Cuándo: hay que calcular coordenadas, distancias, rumbos o áreas a partir de puntos dados. No para: formatear coordenadas decimales como grados, minutos y segundos (coordinates-to-dms). 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: Parses latitude/longitude written as DMS (4°38'8"N), degrees-decimal-minutes (4°38.13'N), decimal with hemisphere letters (N/S/E/W, O for oeste) or signs, into signed decimal degrees. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: formatting decimal coordinates as degrees, minutes and seconds (coordinates-to-dms). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude text (string; required; up to 64 chars).
longitudeYesLongitude text (string; required; up to 64 chars).

Output Schema

NameRequiredDescriptionDefault
latNo
lonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / latitude / examples
      Added value: +[
+  "4°42'39.6\"N"
+]
    • addedInput schema / properties / longitude / examples
      Added value: +[
+  "74°04'19.6\"W"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Parses latitude/longitude written as DMS (4°38'8\"N), degrees-decimal-minutes (4°38.13'N), decimal with hemisphere letters (N/S/E/W, O for oeste) or signs, into signed decimal degrees. When: coordinates, distances, bearings or areas have to be computed from given points. Not for: formatting decimal coordinates as degrees, minutes and seconds (coordinates-to-dms). 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."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description goes beyond by adding determinism and concrete limits (64 KB input, 1 s per call, 1 MB result), which are genuinely useful operational context an agent cannot get from annotations.

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

Conciseness3/5

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

Content is front-loaded and well-organized, but the description is bilingual and largely duplicated in the schema description (with an explicit pointer to it), which is redundant bulk. Every sentence is relevant, but the repetition costs structure points.

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?

With rich annotations, a complete schema, and an existing output schema, the description covers purpose, alternatives, side effects, and limits thoroughly. Nothing an agent needs to call it correctly is missing; only minor redundancy keeps it from a 5.

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% and both latitude/longitude carry descriptions plus examples, so the schema does the heavy lifting. The description lists input formats but adds little parameter-specific meaning beyond what the schema and examples already convey; 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 (convert) and resource (DMS/decimal-minutes/hemisphere coordinates to signed decimal degrees), enumerates all accepted input formats, and explicitly distinguishes itself from the coordinates-to-dms sibling. An agent can identify exactly what this does without opening the schema.

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?

Explicitly provides a 'Cuándo/When' clause (computing coordinates, distances, bearings, areas from given points) and a 'No para/Not for' clause naming coordinates-to-dms as the alternative. The selection condition is unambiguous.

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