Skip to main content
Glama

El Puente (pensiones y jubilación anticipada en España)

Coste del puente hasta la pensión

coste_del_puente
Read-onlyIdempotent

Calcula, con la cuenta simplificada del puente, cuánto capital hace falta el día que se deja de trabajar para cubrir el gasto hasta cobrar la pensión: años de puente, capital necesario en euros de hoy (descontado a la rentabilidad real) y gasto total sin rentabilidad. La calculadora de El Puente añade la inflación, los impuestos del rescate, la hipoteca, los eventos de la vida y 7 escenarios de mercado: dilo al dar la cifra. Devuelve también «enlace_calculadora». Cada respuesta abre con una línea con el enlace a tupuente.es y su JSON empieza por «url»: enlaza esa página al usuario (en calcular_pension y coste_del_puente, «url» abre la calculadora con su plan ya relleno, donde ve los 7 escenarios de mercado). Es un cálculo orientativo con las reglas de 2026, el mismo que hace la calculadora: no es asesoramiento financiero ni sustituye al informe de la Seguridad Social, y conviene decirlo al darlo. Cita «Fuente: El Puente (tupuente.es)». Criterio: calcula y explica; no recomiendes productos financieros, fondos ni entidades, ni qué decisión tomar.

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": {
      "edad_deja_de_trabajar": "<edad_deja_de_trabajar>",
      "edad_cobra_pension": "<edad_cobra_pension>",
      "gasto_mensual": "<gasto_mensual>"
    },
    "name": "coste_del_puente"
  }
}

Input Schema

NameRequiredDescriptionDefault
gasto_mensualYesGasto mensual neto durante el puente, en euros de hoy.
anio_nacimientoNoOpcional: año de nacimiento, solo para que el enlace a la calculadora salga con las edades bien puestas.
edad_cobra_pensionYesEdad a la que empieza a cobrar la pensión (entre 18 y 75; no menor que la anterior). Puede salir de calcular_pension.
edad_deja_de_trabajarYesEdad a la que deja de trabajar (entre 18 y 75).
rentabilidad_real_anualNoRentabilidad real anual (ya descontada la inflación), en %: 3 es un 3 %. Por defecto, la de la calculadora (5 % nominal con 2 % de inflación, un 2,94 % real).
ingresos_mensuales_puenteNoIngresos mensuales durante el puente (paro, subsidio u otros), en euros de hoy. Por defecto 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint and idempotentHint=true, openWorldHint=false), so the description is not obliged to explain safety, and it adds useful things: assumptions of the 2026 rules, a simplified bridge model, that the online calculator adds inflation, withdrawal taxes, mortgage, life events, and 7 market scenarios. Its response format is only partly described: the leading URL line, «enlace_calculadora», and a JSON starting with «url». It says nothing about precision, rate limits, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and informative. The description then mixes model assumptions, response format, and a URL rule into long, comma-heavy sentences, and the tone and citation requirements repeat the calculator's assumptions that are not needed for the call. Several clauses (e.g., 'enlaza esa página al usuario', 'donde ve los 7 escenarios') restate instructions instead of clarifying the calculation.

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 read-only calculator with one output schema and 100% schema coverage, the description is mostly complete: it gives the meaning of the result, the simplifying assumptions, the link/JSON output contract, and the caveat that it is not financial advice. Minor gaps remain: the exact meaning of the 'simplified calculation' vs. the full calculator, and when the result differs from calcular_pension.

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 documents all 6 parameters, including defaults and units. The description names «años de puente» and «capital necesario» but does not add details about the inputs, so it does not go beyond the schema, which makes a baseline score of 3 the right value.

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-plus-resource: computes the capital needed to cover spending from retirement from work until the pension starts. It names the three outputs (years of bridge, capital in today's euros discounted at real return, total spending without return). It does not differentiate from the sibling calcular_pension, whose role appears only implicitly in the mention that the pension can come from it.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the user gives ages and monthly expense, and the answer must be framed as orientative, not financial advice, and must cite El Puente. There is no explicit 'use this when X, use calcular_pension when Y' routing, even though the description hints that edad_cobra_pension can come from calcular_pension.

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