Burs-IA Utils

Convertir masa

convert-mass

Read-onlyIdempotent

Convierte masa entre unidades (kg, g, mg, ug, t, lb, oz, st, short_ton, long_ton, ct, libra_co, arroba_co). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir densidad entre unidades (convert-density). 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 mass between units (kg, g, mg, ug, t, lb, oz, st, short_ton, long_ton, ct, libra_co, arroba_co). 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 density between units (convert-density). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`to`	No	Target unit (omit for all) (string; optional; up to 20 chars).
`from`	Yes	Source unit: kg, g, mg, ug, t, lb, oz, st, short_ton, long_ton, ct, libra_co, arroba_co (string; required; up to 20 chars).
`value`	Yes	Value to convert (number; required).

Output Schema

Name	Required	Description
`to`	No
`from`	No
`value`	No	any JSON value
`result`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / from / examples
```
Added value: +[
+  "lb"
+]
```
- addedInput schema / properties / value / examples
```
Added value: +[
+  1
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Converts mass between units (kg, g, mg, ug, t, lb, oz, st, short_ton, long_ton, ct, libra_co, arroba_co). 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 density between units (convert-density). 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.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 baseline is covered; the description adds real value with operational limits (64 KB input, 1 s per call, 1 MB result), determinism, and 12-significant-digit output precision. It does not repeat the safety hints redundantly beyond a brief confirmation, and the output schema covers return shape.

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 content is well front-loaded and clearly labeled (Cuándo / No para / Efectos secundarios / Determinista / Límites), but the entire body is duplicated verbatim in Spanish and English, roughly doubling length with zero new information. The trailing "[EN completo / full EN: inputSchema.description]" fragment is also noise rather than content.

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 simple 3-parameter, 2-required conversion tool with a full output schema and rich annotations, everything needed to call it correctly is present: units, default behavior, precision, limits, and the sibling exclusion.

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 the unit enumeration, examples and "omit for all" note all already appear in the schema. The description's only marginal addition is restating that omitting "to" returns every unit, so the baseline of 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 and resource ("Convierte masa entre unidades") and enumerates the full unit set, which pins down the scope unambiguously among the many sibling convert-* tools. It also explicitly names the adjacent-but-different tool (convert-density), so an agent can distinguish it 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?

Provides an explicit "Cuándo" trigger (converting a quantity between units with exact definitional factors) and an explicit "No para" exclusion routing to convert-density. The "Without 'to', every unit is returned" note also tells the agent how to use the tool in its two modes.

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?