Burs-IA Utils

Cuota de un préstamo

fin-loan-payment

Read-onlyIdempotent

Calcula la cuota fija de un préstamo amortizable (anualidad), total pagado e intereses. 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 tabla de amortización completa (fin-loan-amortization). 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 fixed periodic payment for an amortizing loan: PMT = P·r / (1 − (1 + r)^−n), with total paid and total interest. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the full amortization schedule (fin-loan-amortization). 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

Name	Required	Description
`periods`	Yes	Number of payments (integer; required; min 1; max 1200).
`principal`	Yes	Loan amount (number; required; min 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
`total_paid`	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.06
+]
```
- addedInput schema / properties / periods / examples
```
Added value: +[
+  360
+]
```
- addedInput schema / properties / principal / examples
```
Added value: +[
+  200000
+]
```
First observedNov 1, 2026

TDQS

A4.2/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 restating "read-only, no network, no state" is largely redundant. It does add genuinely new disclosure: determinism (same input, same output) and hard limits (64 KB input, 1 s per call, 1 MB result) that no structured field carries.

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?

Front-loaded with purpose, then cleanly sectioned into When / Not for / Effects / Deterministic / Limits, which makes scanning easy. The one cost is that the entire block is duplicated in Spanish and English, roughly doubling length for an agent that only needs one language.

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, annotations cover the safety profile, and the description still covers formula, determinism, exclusions and operational 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented, and the baseline of 3 applies. The formula adds some connective meaning between principal, rate and periods, but it leaves r ambiguous (annual vs. periodic) and never mentions periods_per_year, so it does not meaningfully extend 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?

Names the exact resource and computation (fixed periodic payment for an amortizing loan) and even gives the closed-form formula, so an agent knows precisely what comes back (payment, total paid, total interest). It explicitly distinguishes itself from fin-loan-amortization, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"When" and "Not for" are stated explicitly, and the amortization-schedule alternative is named, which is the highest-risk confusion. The "when" clause itself is fairly generic financial-math language that could also describe fin-tvm, fin-compound-interest or fin-simple-interest, so routing among the other finance siblings is not fully resolved.

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?