Burs-IA Utils

Tabla de amortización

fin-loan-amortization

Read-onlyIdempotent

Calcula la tabla de amortización completa (cuota, interés, capital, saldo) hasta 600 periodos. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: calcular la cuota fija de un préstamo amortizable (fin-loan-payment). 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: Computes the full amortization schedule (payment, interest, principal, balance per period) for a fixed-payment loan, up to 600 rows; the last payment absorbs rounding. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the fixed periodic payment for an amortizing loan: PMT = P·r / (fin-loan-payment). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`periods`	Yes	Number of payments (integer; required; min 1; max 600).
`principal`	Yes	Loan amount (number; required; > 0).
`annual_rate`	Yes	Annual nominal rate, decimal (number; required; min 0; max 10).
`periods_per_year`	No	Payments per year (integer; optional; default 12; min 1; max 365).

Output Schema

Name	Required	Description	Default
`payment`	No
`schedule`	No
`total_interest`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / annual_rate / examples
```
Added value: +[
+  0.12
+]
```
- addedInput schema / properties / periods / examples
```
Added value: +[
+  3
+]
```
- addedInput schema / properties / principal / examples
```
Added value: +[
+  1000
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes the full amortization schedule (payment, interest, principal, balance per period) for a fixed-payment loan, up to 600 rows; the last payment absorbs rounding. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the fixed periodic payment for an amortizing loan: PMT = P·r / (fin-loan-payment). 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.3/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, yet the description adds real behavior beyond them: the last payment absorbs rounding, output is deterministic, and hard limits (64 KB input, 1 s per call, 1 MB result). The 'no side effects / read-only / no network' sentence largely restates the annotations, so it is not a full 5.

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?

The EN block is well front-loaded with purpose, then labeled When / Not for / Side effects / Limits, but the entire content is duplicated in Spanish, roughly doubling token cost with no added information for the agent. Structure is good; duplication keeps it from earning a 5.

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 not be described. For a pure deterministic calculator, the description covers selection, the rounding caveat, and operational limits, leaving nothing an agent needs in order to invoke it 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 coverage is 100%, so principal, annual_rate, periods and periods_per_year are already documented in the schema; the description only adds the 600-row ceiling and the rounding convention. That is the expected baseline value, not extra parameter meaning.

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 ('computed the full amortization schedule: payment, interest, principal, balance per period') with scope ('up to 600 rows', 'fixed-payment loan'). It explicitly separates itself from the closest sibling, fin-loan-payment, so an agent can pick correctly without opening schemas.

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 'When:' (exact, reproducible money/tax/financial-math results with rounding and cents) and 'Not for:' routing the fixed periodic payment calculation to fin-loan-payment. Both the positive trigger and the exclusion are stated, not implied.

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?