Skip to main content
Glama

Aurio Calculators

Simular ahorro

simular_ahorro
Read-onlyIdempotent

Proyecta cuánto tendrás ahorrando cada mes con interés compuesto: saldo final, total aportado e intereses ganados. Úsala para “cuánto tendré si ahorro 200 € al mes”, “interés compuesto”, “cuánto gano en 10 años con un 3 %”. English: savings / compound interest projection with monthly contributions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "aportacionInicial": "<aportacionInicial>",
      "aportacionMensual": "<aportacionMensual>",
      "rentabilidadAnual": "<rentabilidadAnual>",
      "anios": "<anios>"
    },
    "name": "simular_ahorro"
  }
}

Input Schema

NameRequiredDescriptionDefault
aniosYesAños ahorrando. Years.
aportacionInicialYesCantidad inicial en euros (0 si empiezas de cero). Initial amount in EUR.
aportacionMensualYesAportación mensual en euros. Monthly contribution in EUR.
rentabilidadAnualYesRentabilidad anual esperada en %, p. ej. 3 (cuenta remunerada) o 6 (fondo indexado). Annual return in %.

Output Schema

NameRequiredDescriptionDefault
ctaYes
kindYes
aniosYes
evolucionYes
interesesYes
disclaimerYes
saldoFinalYes
totalAportadoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the result components and frames it as a projection, but says nothing about modelling assumptions that materially change the numbers (whether contributions are monthly-end, whether the annual rate is compounded monthly) or determinism beyond what annotations state.

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?

Two sentences, front-loaded with the core projection and followed by intent examples; every clause carries signal. The appended English gloss is somewhat redundant given the bilingual schema but is a defensible cross-lingual matching aid rather than filler.

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?

With an output schema present the description need not explain return values, and annotations cover the safety profile, so the definition is nearly sufficient. The one real gap is the compounding/contribution-timing assumption, which an agent cannot infer from schema or annotations and which affects how it should explain results to a user.

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 every parameter carries a bilingual description with ranges, so the schema already does the semantic work. The description only echoes two of the four inputs through examples (200 €/mes, 3 %), adding no interpretation the schema lacks; the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Proyecta cuánto tendrás ahorrando cada mes con interés compuesto') and enumerates the three outputs (saldo final, total aportado, intereses ganados), so an agent knows exactly what the tool computes. It does not name or contrast any sibling (simular_hipoteca, me_lo_puedo_permitir), leaving differentiation to the resource noun alone.

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?

Provides concrete trigger phrasings an agent can match against user intent ('cuánto tendré si ahorro 200 € al mes', 'interés compuesto', 'cuánto gano en 10 años con un 3 %'), which is clear positive guidance on when to call it. There is no explicit exclusion or pointer to an alternative for adjacent questions such as affordability (me_lo_puedo_permitir) or mortgage simulation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources