Skip to main content
Glama

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

De pensión bruta a neta

pension_neta
Read-onlyIdempotent

Pasa una pensión bruta a neta con la misma función de IRPF que usa la calculadora de El Puente: neto anual, neto al mes (anual ÷ 12), IRPF efectivo y los supuestos (persona sola de 65 años o más, sin otras rentas, escala combinada aproximada; no aplica la reducción del art. 20). Indica la bruta anual o la mensual de cada una de las 14 pagas. Enlaza a la guía del IRPF de la pensión. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pension_neta"
  }
}

Input Schema

NameRequiredDescriptionDefault
mensual_14_pagasNoPensión bruta de cada una de las 14 pagas, en euros (se multiplica por 14). Usa esta o pension_bruta_anual, no las dos.
pension_bruta_anualNoPensión bruta de todo un año, en euros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world calculation, and the description adds substantial context beyond them: the response opens with a line containing the tupuente.es link, the JSON starts with «url», the calculation follows 2026 rules and mirrors the website's calculator, and the tool is orientative rather than financial advice. It also states the citation requirement and the advice-giving boundary, which no annotation covers.

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?

Purpose is front-loaded and the sentence order (what it computes → assumptions → inputs → output/link → disclaimer → citation) is logical. It runs long and carries some boilerplate about how other tools' «url» field works, which is relevant but not strictly this tool's job.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an output-schema-less calculator, the description covers methodology, assumptions, input shape, return structure and the disclaimer/citation the agent must relay. Nothing needed to invoke it or to present results correctly is missing.

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% and both parameters already document their ranges, the ×14 multiplication and the 'use one, not both' rule. The description restates the same annual-or-monthly choice without adding format or edge-case detail beyond the schema, so baseline 3 applies.

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 and resource (convert a gross pension to net) and enumerates the exact outputs: neto anual, neto al mes, IRPF efectivo and the assumptions used. It also differentiates itself from the sibling calcular_pension by explaining how each tool's «url» behaves, so an agent can distinguish them without opening the schemas.

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?

Gives clear context for use: person alone aged 65+, no other income, approximate combined scale, art. 20 reduction not applied, and it directs the agent to supply either the annual or the monthly-per-14-pagas figure. It stops short of an explicit 'use X instead when Y' exclusion versus calcular_pension, but the applicable scope and caveats are well defined.

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