Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir presión

convert-pressure
Read-onlyIdempotent

Convierte presión entre unidades (Pa, hPa, kPa, MPa, bar, mbar, atm, psi, mmHg, inHg, torr). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir fuerza entre unidades (convert-force). 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 pressure between units (Pa, hPa, kPa, MPa, bar, mbar, atm, psi, mmHg, inHg, torr). 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 force between units (convert-force). 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: Pa, hPa, kPa, MPa, bar, mbar, atm, psi, mmHg, inHg, torr (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: +[
+  "atm"
+]
    • addedInput schema / properties / value / examples
      Added value: +[
+  1
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint/openWorldHint, yet the description still adds real value: no network, no stored state, determinism, 12-significant-digit precision, and concrete limits (64 KB input, 1 s per call, 1 MB result). These are traits annotations cannot express.

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?

Each sentence is substantive and front-loaded with purpose, then constraints. The only inefficiency is the full Spanish/English duplication, which doubles length, though the dual-language presentation is defensible given the Spanish title and description pairing.

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, return format needn't be described; the description instead covers precision, determinism, and operational limits, which is exactly the residual information an agent needs. A simple conversion tool is fully specified here.

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% and already lists the units per parameter, so the schema carries most of the burden. The description adds the meaningful behavior that omitting 'to' returns every unit, which clarifies the optional parameter's semantics beyond the schema's terse '(omit for all)'.

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 presión entre unidades') and enumerates the supported units, so scope is unambiguous. It also names the tool it is not ('No para: convertir fuerza entre unidades (convert-force)'), distinguishing it from the other convert-* siblings.

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?

Has an explicit 'When:' clause (converting a quantity between units with exact definitional factors) and an explicit 'Not for:' exclusion routing to convert-force. Nothing about tool selection is left 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 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