Burs-IA Utils

Convertir tasa de interés (EA, nominal)

interest-rate-convert

Read-onlyIdempotent

Convierte tasas entre efectiva anual (EA), nominal anual (p. ej. NMV) y efectiva periódica, vencidas o anticipadas. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: convertir un salario entre hora, mes y año (salary-convert). 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 interest rates between effective annual (EA/APY), nominal annual compounded m times (APR, e.g. NMV monthly in Colombia) and effective periodic rates, for advance or arrears payment. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: converting pay between hourly, monthly and annual figures (salary-convert). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`from`	Yes	Given rate type (required; one of: effective_annual, nominal_annual, effective_periodic).
`in_advance`	No	Rate is anticipada (paid in advance) (boolean; optional; default false).
`rate_percent`	Yes	Rate % (number; required; min -99; max 10000).
`periods_per_year`	No	Compounding periods per year (12 = monthly) (integer; optional; default 12; min 1; max 365).

Output Schema

Name	Required	Description	Default
`periods_per_year`	No
`nominal_annual_percent`	No
`effective_annual_percent`	No
`effective_periodic_percent`	No
`periodic_in_advance_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / from / examples
```
Added value: +[
+  "effective_annual"
+]
```
- addedInput schema / properties / rate_percent / examples
```
Added value: +[
+  24
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Converts interest rates between effective annual (EA/APY), nominal annual compounded m times (APR, e.g. NMV monthly in Colombia) and effective periodic rates, for advance or arrears payment. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: converting pay between hourly, monthly and annual figures (salary-convert). 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."

First observedNov 1, 2026

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, non-destructive and closed-world, so the safety profile is covered; the description still adds determinism ('la misma entrada da la misma salida') and concrete operational limits (64 KB input, 1 s per call, 1 MB result). Those runtime bounds are exactly the kind of context structured fields do not carry.

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?

The Spanish block is front-loaded and dense, with scope first and limits last. However, the full 'EN:' restatement and the trailing '[EN completo / full EN: inputSchema.description]' pointer duplicate content already present, costing space without adding 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?

An output schema exists, so return values need no explanation; the description covers purpose, selection criteria, exclusions, side-effect profile, determinism and size/time limits. Nothing an agent needs in order to call this correctly is missing.

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 nevertheless adds conceptual meaning by explaining that nominal annual means compounded m times (APR, e.g. Colombian NMV) and that rates may be vencidas or anticipadas, which clarifies how 'from' and 'in_advance' interact. It stops short of tying periods_per_year explicitly to the nominal case.

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 (interest rates) plus the exact scope: effective annual, nominal annual compounded m times, and effective periodic, in advance or arrears. It explicitly names the tool it is not (salary-convert), so an agent can rule out a plausible-looking sibling 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?

Uses an explicit 'Cuándo:' condition (financial math that must be exact and reproducible) and an explicit 'No para:' exclusion pointing at salary-convert. When-to-use, when-not-to-use and the alternative are all stated, leaving nothing 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 tools Inspect

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

Need Help?