Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir unidades de tiempo

convert-time
Read-onlyIdempotent

Convierte tiempo entre unidades (ns, us, ms, s, min, h, d, wk, month, yr, decade, century). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: analizar una duración ISO 8601 (duration-parse). 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 time between units (ns, us, ms, s, min, h, d, wk, month, yr, decade, century). 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: parsing an ISO 8601 duration (duration-parse). 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: ns, us, ms, s, min, h, d, wk, month, yr, decade, century (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: +[
+  "min"
+]
    • addedInput schema / properties / value / examples
      Added value: +[
+  90
+]
  2. First observed

TDQS

A4.6/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 the safety profile is covered. The description still adds non-trivial operational context: determinism, exact definitional factors, 12 significant digits, and hard limits (64 KB input, 1 s per call, 1 MB result) that the annotations do not carry. Slight redundancy in restating 'no side effects' keeps it from a 5.

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?

Content is front-loaded (what it does, then When / Not for / Side effects / Deterministic / Limits) and every section is actionably short. The main inefficiency is that the entire block is duplicated verbatim in Spanish and English, roughly doubling length, and the 12-significant-digit detail appears only in the EN copy.

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 pure, deterministic conversion utility the definition covers everything an agent needs: unit vocabulary, default behavior, exactness/precision, resource limits, and the alternative tool. An output schema exists, so return-value shape need not be described.

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; the description earns a bump by clarifying the semantics of omitting 'to' (all units returned) and by stating the numeric contract (exact definitional factors, results to 12 significant digits). The supported-unit list mirrors the 'from' schema description, so most of the value is the rounding/precision behavior, which is genuinely beyond the schema.

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+resource ('Convierte tiempo entre unidades') and enumerates the exact unit set (ns through century), plus the default behavior when 'to' is omitted. It also names the sibling it is not (duration-parse), so an agent can separate it from the other time-related tools in a huge sibling list.

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 gives the positive condition (converting a quantity between units with exact definitional factors) and an explicit 'No para' exclusion routing ISO 8601 duration parsing to duration-parse. That is the full when/when-not/alternative triad.

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