Burs-IA Utils

Convertir par de torsión

convert-torque

Read-onlyIdempotent

Convierte par de torsión entre unidades (N·m, kN·m, lbf·ft, lbf·in, kgf·m). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir energía entre unidades (convert-energy). 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 torque between units (N·m, kN·m, lbf·ft, lbf·in, kgf·m). 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 energy between units (convert-energy). 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
`to`	No	Target unit (omit for all) (string; optional; up to 20 chars).
`from`	Yes	Source unit: N·m, kN·m, lbf·ft, lbf·in, kgf·m (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: +[
+  "N·m"
+]
```
- addedInput schema / properties / value / examples
```
Added value: +[
+  100
+]
```
First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing operational limits (64 KB JSON input, 1 s per call, 1 MB result), determinism, and output precision (12 significant digits). The 'no side effects / read-only' sentence largely restates readOnlyHint and destructiveHint, which slightly dilutes the added value.

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?

Purpose is front-loaded and each sentence carries information (units, default behavior, when/when-not, limits). The full Spanish/English duplication roughly doubles the length, which is a structural cost even if intentional for locale coverage.

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?

An output schema exists, annotations fully declare the safety profile, and the description still supplies precision, default-return behavior, and runtime limits. Nothing an agent needs to invoke this 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 is 3, but the description adds a genuinely behavioral detail the schema only hints at: omitting 'to' returns every unit rather than erroring. It does not add syntax guidance for unit string spelling beyond the already-listed names.

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 torque between units) and enumerates the supported units, so scope is unambiguous. It also names the sibling it is not for (convert-energy), which matters in a catalog with ~15 other convert-* tools.

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 'When:' clause (quantity must be converted using exact definitional factors) plus an explicit 'Not for:' exclusion pointing to convert-energy. The alternative and the condition selecting it are both named, leaving nothing to inference.

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?