Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir longitud

convert-length
Read-onlyIdempotent

Convierte longitud entre unidades (m, km, cm, mm, um, nm, mi, yd, ft, in, nmi, au, ly). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir área entre unidades (convert-area). 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: Converts length between units (m, km, cm, mm, um, nm, mi, yd, ft, in, nmi, au, ly). Without "to", every unit is returned. Exact definitional factors; results to 12 significant digits. When: a quantity has to be converted between units with exact definitional factors. Not for: converting area between units (convert-area). 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

NameRequiredDescriptionDefault
toNoTarget unit (omit for all) (string; optional; up to 20 chars).
fromYesSource unit: m, km, cm, mm, um, nm, mi, yd, ft, in, nmi, au, ly (string; required; up to 20 chars).
valueYesValue to convert (number; required).

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
valueNoany JSON value
resultNoany JSON value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from / examples
      Added value: +[
+  "mi"
+]
    • addedInput schema / properties / value / examples
      Added value: +[
+  1
+]
  2. First observed

TDQS

A4.4/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, and the description partly restates them ("solo lectura, sin red, sin estado guardado", "determinista"). It earns credit for information absent from annotations: the 64 KB input cap, 1 s per-call budget, 1 MB result cap, and output rounded to 12 significant digits.

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 and well ordered: purpose, unit list, default behavior, when/when-not, limits. The cost is full bilingual duplication — the same content appears in Spanish and English, roughly doubling length without adding 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?

For a small 3-parameter conversion tool with an output schema, full annotation coverage and 100% schema descriptions, nothing an agent needs is missing: units, default behavior, determinism, precision and resource limits are all stated, so return values need no further explanation.

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 coverage is 100% and the schema already documents all three params, including "omit for all" for `to` and the full unit list for `from`; the "Sin 'to' devuelve todas" line merely restates that. No additional semantic detail (e.g. case sensitivity of unit codes, error behavior on unknown units) is added, so baseline 3 is right.

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 ("Convierte longitud") and enumerates all 13 supported units, so the scope is unambiguous. It also explicitly separates itself from the most confusable sibling (convert-area), which lets an agent pick the right tool without opening either 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?

Provides an explicit "When" clause and an explicit "No para" exclusion naming convert-area. All three slots (when, when-not, alternative) are filled, leaving nothing to inference for the adjacent-conversion case.

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