Burs-IA Utils

Interés simple

fin-simple-interest

Read-onlyIdempotent

Calcula el interés simple I = P·r·t y monto total, con tiempo en años, meses o días. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: calcular el valor futuro con interés compuesto (fin-compound-interest). 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 simple interest I = P·r·t and the total amount, with time in years, months or days (actual/365 or 360 basis). When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the future value with compound interest (fin-compound-interest). 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	Default
`time`	Yes	Time (number; required; min 0; max 100000).
`unit`	No	Time unit (optional; one of: years, months, days; default "years").	years
`day_basis`	No	Days per year (optional; one of: 365, 360; default "365").	365
`principal`	Yes	Principal (number; required; min 0).
`annual_rate`	Yes	Annual rate, decimal (number; required; min 0; max 10).

Output Schema

Name	Required	Description	Default
`total`	No
`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.05
+]
```
- addedInput schema / properties / principal / examples
```
Added value: +[
+  1000
+]
```
- addedInput schema / properties / time / examples
```
Added value: +[
+  3
+]
```
First observedNov 1, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the basic annotations (readOnlyHint, deterministic), the description discloses vital operational constraints like computational limits (64 KB input, 1 s per call), deterministic behavior, and the specific handling of the time basis (365 or 360). This level of operational detail is highly valuable for a financial utility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is dense but highly efficient. It places the core function (calculation/formula) first, followed by usage context, warnings, and technical constraints in a logical flow. No sentence is redundant.

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?

Given the complexity of financial calculations involving multiple interacting parameters (time units, basis, principal, rate), the description covers all necessary ground. It informs the agent about the calculation logic, acceptable inputs, and the scope of its use within the available financial tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Although the schema is 100% covered, the description adds critical domain knowledge. It clarifies the meaning of 'time' (years, months, days) and explains the necessity of the 'day basis' (365 or 360), which are specific to financial calculation methods.

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?

The tool's purpose is explicitly stated by providing the formula (I = P·r·t) and describing the exact calculation of simple interest. Crucially, it identifies 'fin-compound-interest' as the relevant sibling it is not, preventing ambiguity in tool selection.

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?

It provides highly specific usage conditions ('when') and explicit exclusions ('Not for: computing the future value with compound interest'). This clearly gates the application of the tool to only appropriate financial contexts.

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?