Skip to main content
Glama
MITDEVPRO

finanzas-mcp

by MITDEVPRO

interes_compuesto

Read-onlyIdempotent

Compute future or present value using compound interest with optional periodic contributions. Determine final amount or required initial capital.

Instructions

Interés compuesto: valor futuro o presente, con aportes periódicos opcionales.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capitalYesCapital inicial (VP) o meta final (VF) según 'calcular'
calcularNo'vf' (valor futuro de capital+aportes) o 'vp' (valor presente de la meta)vf
periodosYesNúmero de períodos
tasa_periodoYesTasa por período, decimal
aporte_periodicoNoAporte al final de cada período (anualidad ordinaria)
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating safe computation. Description adds 'valor futuro o presente' but no further behavioral traits beyond what annotations provide.

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?

A single, concise sentence that front-loads the key purpose and optionality. Every word is necessary and no redundancy.

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?

For a simple calculation tool with full schema coverage and safe annotations, the description is sufficient. It lacks return value details, but annotations imply a numerical result. Slightly more context on output would improve completeness.

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 field descriptions in the schema are comprehensive. The description mentions 'aporte periódicos opcionales', reinforcing the optional nature of aporte_periodico, but adds no new semantic value beyond 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?

Description clearly states 'Interés compuesto: valor futuro o presente, con aportes periódicos opcionales.' This explicitly identifies it as a compound interest calculator for future or present value with optional periodic contributions. It distinguishes well from sibling financial tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention exclusions or provide context for selection among the many sibling financial tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MITDEVPRO/finanzas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server