Delegum

calcular_amortizacion_anticipada

Read-only

Calcula el efecto de amortizar anticipadamente una hipoteca o préstamo (sistema francés). Compara las dos opciones del banco —reducir la cuota mensual o reducir el plazo— con el ahorro de intereses de cada una y recomienda la más ventajosa.

Input Schema

TableJSON Schema

Name	Required	Description
`tin`	Yes	Tipo de interés nominal anual (TIN) en %
`plazo_anios`	Yes	Plazo original del préstamo en años
`fecha_inicio`	No	Fecha de inicio del préstamo (YYYY-MM-DD), alternativa a meses_transcurridos
`capital_inicial`	Yes	Capital original del préstamo o hipoteca en euros
`fecha_amortizacion`	No	Fecha de la amortización anticipada (YYYY-MM-DD)
`meses_transcurridos`	No	Meses transcurridos desde el inicio del préstamo hasta la amortización (alternativa a las fechas)
`importe_amortizacion`	Yes	Importe que se amortiza anticipadamente en euros

TDQS

A4.2/5.0

Behavior4/5

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

The description adds behavioral context: it not only calculates but also compares options and recommends. Annotations indicate readOnlyHint=true, which is consistent. No contradictions. However, it does not discuss edge cases or error handling.

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?

Two sentences, concise, front-loaded with the purpose. Every word is necessary and no 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?

Given no output schema, the description mentions the output includes interest savings and a recommendation, which is sufficient. It could briefly mention the output format, but overall it is complete enough for the complexity.

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 coverage is 100%, so the schema already describes all parameters. The description adds a high-level explanation of what the tool does (compare options) but does not add specific parameter meaning beyond the schema. Baseline 3 is appropriate.

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 description clearly states it calculates the effect of early amortization for a mortgage (French system), compares two options (reduce monthly payment or reduce term), and recommends the best option. It is a specific verb+resource and distinguishes from sibling financial calculators.

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?

The description implies the use case (early amortization of a mortgage) but lacks explicit when-to-use or when-not-to-use guidance or alternatives. It is clear enough for the context but could be improved with exclusions.

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

All Delegum tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.

Naming Consistency5/5

All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.

Tool Count3/5

49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.

Completeness4/5

The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).

Resources

Need Help?