Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Convertir ángulo

convert-angle
Read-onlyIdempotent

Convierte ángulo entre unidades (rad, deg, grad, turn, arcmin, arcsec, mrad). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: formatear coordenadas decimales como grados, minutos y segundos (coordinates-to-dms). 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 angle between units (rad, deg, grad, turn, arcmin, arcsec, mrad). 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: formatting decimal coordinates as degrees, minutes and seconds (coordinates-to-dms). 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

NameRequiredDescriptionDefault
toNoTarget unit (omit for all) (string; optional; up to 20 chars).
fromYesSource unit: rad, deg, grad, turn, arcmin, arcsec, mrad (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: +[
+  "deg"
+]
    • addedInput schema / properties / value / examples
      Added value: +[
+  180
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Converts angle between units (rad, deg, grad, turn, arcmin, arcsec, mrad). 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: formatting decimal coordinates as degrees, minutes and seconds (coordinates-to-dms). 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."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description still adds real value beyond them: determinism, 12 significant digits precision, and concrete limits (64 KB input, 1 s per call, 1 MB result). It does not say what happens on an invalid unit string, which is the only notable behavioral gap.

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?

Content is front-loaded and labeled (When / Not for / Side effects / Deterministic / Limits), which aids scanning. However, the entire payload is duplicated in Spanish and English, roughly doubling length for no informational gain, and the EN block even embeds a meta-reference to the schema description.

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, the description needn't explain return values, and it still covers scope, exclusions, determinism, precision and operational limits. An agent has everything required to call this correctly.

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 the schema already documents `value`, `from`, and `to` (including the 'omit for all' behavior and the unit list). The description restates those facts rather than adding syntax or validation detail, so the baseline 3 is appropriate.

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 ("converts angle between units") and enumerates the supported units (rad, deg, grad, turn, arcmin, arcsec, mrad), so an agent knows exactly what domain this covers. It also names the adjacent non-goal (coordinates-to-dms) so it is distinguishable from the closest sibling.

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 (converting a quantity with exact definitional factors) and explicit "Not for:" clause pointing at coordinates-to-dms. Both the positive trigger and the exclusion are stated, which is the top of this dimension's scale.

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