Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir energía

convert-energy
Read-onlyIdempotent

Convierte energía entre unidades (J, kJ, MJ, cal, kcal, Wh, kWh, MWh, BTU, eV, therm, ft_lbf). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir potencia entre unidades (convert-power). 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 energy between units (J, kJ, MJ, cal, kcal, Wh, kWh, MWh, BTU, eV, therm, ft_lbf). 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 power between units (convert-power). 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: J, kJ, MJ, cal, kcal, Wh, kWh, MWh, BTU, eV, therm, ft_lbf (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: +[
+  "kWh"
+]
    • 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, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuine value beyond that: exact definitional factors, 12 significant digits, and concrete limits (64 KB input, 1 s per call, 1 MB result), though it somewhat redundantly restates 'no side effects'/'deterministic' already implied by the annotations.

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 with the core purpose, then cleanly sectioned into When/Not-for/Side effects/Limits. Slightly padded by the full ES/EN duplication and unit enumeration repeated in both the prose and the schema, but each sentence carries 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?

Output schema exists, and the description supplies precision (12 significant digits) and operating limits that an agent needs to call it correctly. Nothing material is missing for a stateless conversion tool.

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%, so all three parameters are already documented. The description adds the meaningful behavior that omitting 'to' returns all units, but otherwise mostly repeats the unit list the schema already contains.

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 (converts) and resource (energy units), enumerates the supported units, and explicitly names the sibling it is not (convert-power). An agent can distinguish it from the other unit converters 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?

Includes an explicit 'When' clause (converting quantities with exact definitional factors) and an explicit 'Not for' clause routing power conversions to convert-power. The 'without "to", every unit is returned' note further guides invocation choice.

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