Burs-IA Utils

TIR con fechas irregulares (XIRR)

fin-xirr

Read-onlyIdempotent

Calcula la TIR anualizada para flujos en fechas irregulares (como XIRR de Excel). 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 tasa interna de retorno de flujos periódicos (fin-irr). 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 annualized internal rate of return for cash flows on arbitrary dates (actual/365, like Excel XIRR). When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the internal rate of return of periodic cash flows (fin-irr). 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
`flows`	Yes	Dated cash flows (array of object; required; at least 2 items; up to 1000 items).

Output Schema

Name	Required	Description	Default
`xirr`	No
`xirr_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / flows / examples

Added value: +[
+  [
+    {
+      "amount": -1000,
+      "date": "2025-01-01"
+    },
+    {
+      "amount": 1100,
+      "date": "2026-01-01"
+    }
+  ]
+]

First observedNov 1, 2026

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 read-only/no-network restatement is partly redundant. The description still adds genuinely new behavioral facts: determinism, the actual/365 day-count convention, and hard 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?

Front-loaded with the core definition and organized into labeled When / Not for / Side effects / Deterministic / Limits segments, so an agent can scan it quickly. The full Spanish-then-English duplication roughly doubles the token cost for no added 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 everything else that matters for calling correctly — date convention, input/output size limits, timeout, determinism, and safety profile. Nothing an agent needs 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 description coverage is 100% and the single `flows` parameter already documents the date/amount shape, min/max items and an example. The description adds only the 'arbitrary dates' framing, which is real but marginal. Baseline 3 applies when the schema carries the parameter burden.

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 — 'Computes the annualized internal rate of return for cash flows on arbitrary dates' — and pins the convention (actual/365, like Excel XIRR). It explicitly names the sibling it is not (fin-irr for periodic flows), so an agent can separate the two without opening either 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?

'When: a money, tax or financial-math result has to be exact and reproducible' gives a positive selection context, and 'Not for: computing the internal rate of return of periodic cash flows (fin-irr)' gives an explicit exclusion plus the alternative. This is the when/when-not/alternative triad in full.

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?