Skip to main content
Glama

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

Buscar una guía de El Puente

buscar_guia
Read-onlyIdempotent

Busca en las guías de El Puente sobre jubilación anticipada, base reguladora, IRPF de la pensión, subsidio de mayores de 52, convenio especial, autónomos, lagunas, rescate del plan de pensiones, despido cerca de la jubilación y más. Devuelve hasta 5 con título, dirección y descripció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

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar_guia"
  }
}

Input Schema

NameRequiredDescriptionDefault
consultaYesPalabras de lo que se busca, p. ej. «subsidio mayores de 52» o «cómo tributa la pensión».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, closed-world read, so the bar is lower, and the description still adds real behavioural context: the result cap (up to 5), the fields returned (título, dirección, descripción), the fact that each response opens with a link line and that the JSON begins with «url», plus the citation requirement. The caveat that this is an orientative calculation under 2026 rules, not financial advice, is boilerplate that does not fit a pure guide search and slightly muddies the behavioural picture.

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

Conciseness2/5

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

It is front-loaded with the right information, but the body is padded with material that does not belong to a search tool: the calculator-prefill parenthetical, the 2026 orientative-calculation disclaimer, the citation rule, and the advice-policy sentence. Several of these would need to be repeated verbatim across tools, which suggests boilerplate rather than tool-specific content.

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 one-parameter, read-only search tool without an output schema, the definition supplies enough: what it searches, how many results, which fields, and the URL convention. The only genuine gap is the unclear relationship between this tool's «url» and the calculator links mentioned in the parenthetical, which an agent may misread.

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?

There is a single parameter with full schema description coverage, including an example query, so the schema already carries the burden. The description compensates indirectly by enumerating searchable topics, which effectively teaches the query vocabulary, but it adds no constraints on phrasing, synonyms, or result ranking.

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 ("Busca en las guías de El Puente") and enumerates the topic space (jubilación anticipada, base reguladora, IRPF de la pensión, subsidio de mayores de 52, convenio especial, autónomos, lagunas, rescate del plan de pensiones, despido cerca de la jubilación), which clearly frames what the tool covers and differentiates it from the calculator siblings. The clarity is diluted by the inserted passage about calcular_pension and coste_del_puente opening a prefilled calculator, which belongs to a different tool's behaviour and makes the scope momentarily ambiguous.

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?

The topic list implicitly tells the agent when this tool is the right entry point, and the note that the «url» field can open a prefilled calculator hints at a follow-up path. However, there is no explicit when-to-use/when-not guidance versus ver_parametros_2026, pension_neta, or calcular_pension, and no statement of what to do when the search returns nothing. Usage is implied rather than directed.

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