Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Redondear número

round-number
Read-onlyIdempotent

Redondea a N decimales con aritmética decimal exacta y modos half_up, half_even (bancario), up, down, ceiling, floor. Cuándo: un resultado numérico tiene que ser exacto o reproducible y no estimado. No para: redondear un número a N cifras significativas, en notación normal y científica (significant-figures). 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: Rounds a number to N decimal places using exact decimal arithmetic (no float drift: 1.005 → 1.01 half-up) with modes half_up, half_even (banker's), half_down, up, down, ceiling, floor. When: a numeric result has to be exact or reproducible instead of estimated. Not for: rounding a number to N significant figures and returning it in plain and scientific notation (significant-figures). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
modeNoRounding mode (optional; one of: half_up, half_even, half_down, up, down, ceiling, floor; default "half_up").half_up
valueYesNumber, or decimal string for exact input (number or string; required; up to 400 chars).
decimalsNoDecimal places (negative rounds to tens, hundreds…) (integer; optional; default 0; min -20; max 20).

Output Schema

NameRequiredDescriptionDefault
textNo
resultNoany JSON value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / value / examples
      Added value: +[
+  1.005
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Rounds a number to N decimal places using exact decimal arithmetic (no float drift: 1.005 → 1.01 half-up) with modes half_up, half_even (banker's), half_down, up, down, ceiling, floor. When: a numeric result has to be exact or reproducible instead of estimated. Not for: rounding a number to N significant figures and returning it in plain and scientific notation (significant-figures). 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.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 the description's 'side effects: none' restates structured data. It does earn credit for genuinely new context: determinism, exact decimal arithmetic with the 1.005 → 1.01 illustration, and concrete limits (64 KB input, 1 s per call, 1 MB result).

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?

Well front-loaded with labeled sections (When / Not for / Side effects / Limits) that make scanning easy. However, the body is bilingual with a duplicated Spanish and English rendering, which roughly doubles length for an audience that only needs one, and the Spanish mode list drops half_down.

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 3-parameter pure-computation tool with an output schema, full annotation coverage and complete schema descriptions, nothing an agent needs is missing. Determinism, limits and the sibling distinction are all covered.

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% and every parameter carries its own description, enum, defaults and bounds, so the baseline is 3. The description adds only the conceptual framing of 'N decimal places' and modes; it does not explain the negative-decimals behavior or string-vs-number tradeoff beyond what the schema already states.

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 ('Rounds a number to N decimal places') plus the exact-arithmetic mechanism and the full mode list. It also names the adjacent-but-different tool (significant-figures), so an agent can separate the two without opening a 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?

Has explicit labeled 'When:' (result must be exact/reproducible, not estimated) and 'Not for:' (significant figures in plain/scientific notation → significant-figures) sections. This is the when/when-not/alternative pattern at full strength.

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