Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir volumen

convert-volume
Read-onlyIdempotent

Convierte volumen entre unidades (l, ml, cl, dl, m3, cm3, gal, qt, pt, cup, fl_oz, tbsp, tsp, imp_gal, imp_pt, imp_fl_oz, bbl, ft3, in3). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir medidas de cocina entre volumen (convert-cooking). 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 volume between units (l, ml, cl, dl, m3, cm3, gal, qt, pt, cup, fl_oz, tbsp, tsp, imp_gal, imp_pt, imp_fl_oz, bbl, ft3, in3). 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 kitchen measures between volume (convert-cooking). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit (omit for all) (string; optional; up to 20 chars).
fromYesSource unit: l, ml, cl, dl, m3, cm3, gal, qt, pt, cup, fl_oz, tbsp, tsp, imp_gal, imp_pt, imp_fl_oz, bbl, ft3, in3 (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: +[
+  "gal"
+]
    • addedInput schema / properties / value / examples
      Added value: +[
+  1
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Converts volume between units (l, ml, cl, dl, m3, cm3, gal, qt, pt, cup, fl_oz, tbsp, tsp, imp_gal, imp_pt, imp_fl_oz, bbl, ft3, in3). 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 kitchen measures between volume (convert-cooking). 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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the 'sin efectos secundarios / solo lectura' sentence is largely redundant. The description does add genuinely new context beyond annotations: determinism, 12-significant-digit precision, and hard limits (64 KB input, 1 s per call, 1 MB result), which materially affect how an agent batches and sizes calls.

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?

The core content is front-loaded and well ordered (units, default behavior, when/not-for, side effects, limits), but the full text is duplicated verbatim in Spanish and English, roughly doubling length with no new information. The trailing '[EN completo / full EN: inputSchema.description]' stub is also noise.

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, annotations covering safety and determinism, and 100% schema coverage, the description supplies everything still needed: unit vocabulary, omit-to semantics, sibling routing, and execution limits. No gap remains that would cause a misinvocation.

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 every property is documented, including 'to' being optional and the full unit list on 'from', so the baseline of 3 applies. The description's 'Sin "to" devuelve todas' adds the useful nuance that omitting the target returns all units rather than nothing, but it does not explain unit aliasing, case sensitivity, or invalid-unit behavior.

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 (converts volume between units) and enumerates the full unit set, so scope is unambiguous. It also names the sibling it is not (convert-cooking) for kitchen measures, letting an agent separate it from the other convert-* tools without opening a 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?

Explicit 'Cuándo:' clause defines the triggering condition (quantity must be converted with exact definitional factors) and an explicit 'No para:' exclusion routing kitchen measures to convert-cooking. This is the when/when-not/alternative pattern in full.

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