Burs-IA Utils

Tasa de crecimiento anual compuesta

fin-cagr

Read-onlyIdempotent

Calcula la tasa de crecimiento anual compuesta (CAGR) y crecimiento total. 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 retorno sobre la inversión y su tasa anualizada (fin-roi). 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 compound annual growth rate CAGR = (end / start)^(1 / years) − 1 and the total growth. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the return on investment and its annualized rate (fin-roi). 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
`years`	Yes	Years (number; required; > 0; max 1000).
`end_value`	Yes	End value (number; required; min 0).
`start_value`	Yes	Start value (number; required; > 0).

Output Schema

Name	Required	Description	Default
`cagr`	No
`cagr_percent`	No
`total_growth_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / end_value / examples
```
Added value: +[
+  200
+]
```
- addedInput schema / properties / start_value / examples
```
Added value: +[
+  100
+]
```
- addedInput schema / properties / years / examples
```
Added value: +[
+  5
+]
```
First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, yet the description still adds determinism, absence of network and stored state, and concrete limits (64 KB input, 1 s per call, 1 MB result) that are not in the annotations. This is behavioral context beyond the structured fields, not a restatement.

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?

Well structured and front-loaded: formula first, then when/not-for/effects/limits. The full Spanish and English duplication doubles the length for the same content, which is the main conciseness cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-value explanation is unnecessary, and the description covers determinism and runtime limits. It does not mention edge outcomes such as a zero end_value or negative growth, which an agent might need to interpret results for a math tool.

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%, so start_value, end_value and years are already documented, giving a baseline of 3. The formula does clarify how the three inputs combine (rate over years), but no per-parameter nuance (e.g. start_value > 0 edge case, end_value = 0) is added beyond the schema constraints.

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 ('Calcula') plus the exact resource and the formula: CAGR = (end / start)^(1 / years) − 1, and adds the total growth. It also explicitly names the sibling it is not (fin-roi), so an agent can distinguish it 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?

Contains explicit 'Cuándo' and 'No para' clauses, routing the agent to fin-roi for ROI/annualized return. The condition that selects this tool (exact, reproducible money/tax/financial-math results) is stated directly.

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?