Skip to main content
Glama
Sign In

Delegum

by com.delegum
OverviewDiscussionsAdmin

calcular_pension_incapacidad

Read-only

Calcula la prestación por incapacidad permanente (parcial, total, absoluta o gran incapacidad, la antigua gran invalidez): base reguladora, porcentaje aplicado, recargo por edad ≥55 años en la incapacidad total y complemento de gran incapacidad. La IP parcial se abona como indemnización a tanto alzado; el resto, como pensión mensual. Si la pensión no llega a la mínima, da el complemento a mínimos máximo posible y el límite de ingresos que lo condiciona, sin sumarlo a la pensión.

Input Schema

NameRequiredDescriptionDefault
edadYesEdad del beneficiario en años (relevante para el recargo del 20% en IP total con ≥55 años)
tiene_conyugeNo¿Tiene cónyuge a cargo? Afecta a la pensión mínima garantizada. Por defecto false.
grado_incapacidadYesGrado de incapacidad permanente declarado. "gran_incapacidad" y "gran_invalidez" son el mismo grado.
origen_contingenciaYes"comun" = enfermedad común o accidente no laboral. "profesional" = accidente de trabajo o enfermedad profesional.
suma_bases_cotizacionYesSuma de las bases de cotización del período de referencia (€). Comunes: últimas 112 mensualidades (8 años). Profesionales: últimas 12 mensualidades.
ultima_base_cotizacionNoÚltima base de cotización mensual (€). Necesaria para el complemento de gran incapacidad.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / grado_incapacidad / description
      Previous value: -"Grado de incapacidad permanente declarado"New value: +"Grado de incapacidad permanente declarado. \"gran_incapacidad\" y \"gran_invalidez\" son el mismo grado."
    • changedInput schema / properties / grado_incapacidad / enum
      Previous value: -[
-  "parcial",
-  "total",
-  "absoluta",
-  "gran_invalidez"
-]New value: +[
+  "parcial",
+  "total",
+  "absoluta",
+  "gran_incapacidad",
+  "gran_invalidez"
+]
    • changedInput schema / properties / ultima_base_cotizacion / description
      Previous value: -"Última base de cotización mensual (€). Necesaria para el complemento de gran invalidez."New value: +"Última base de cotización mensual (€). Necesaria para el complemento de gran incapacidad."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden of behavioral disclosure and does well: it explains that partial disability is paid as a lump sum, others as a monthly pension, and that the minimum complement is returned with its income limit but not added to the pension. This adds genuine calculation behavior beyond the read-only annotation.

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?

A single dense paragraph that front-loads the core purpose and then adds essential calculation details. Every sentence contributes useful information, though the density is high and could be slightly more structured for quick scanning.

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?

No output schema exists, so the description must explain return values. It lists the main outputs (base reguladora, percentage, age surcharge, grand disability complement) and clarifies payment forms and minimum complement handling. It could go further on exact return format, but it is largely complete for a calculator with fully documented inputs.

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?

With schema description coverage at 100%, the schema already documents all six parameters thoroughly, including enums, ranges, and roles. The description does not add parameter-specific details beyond what the schema provides, so the baseline score of 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?

States a specific verb ('Calcula'), a precise resource ('prestación por incapacidad permanente'), and lists all covered grades and components. An agent can easily distinguish it from sibling calculators like calcular_pension_publica because the description enumerates the exact pension type and calculation elements.

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 description implies usage by stating what is calculated, but gives no explicit when-to-use, prerequisites, or alternatives to sibling calculators. For a standalone calculator, the purpose makes usage clear, but there is no guidance on when to choose this over related tools.

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

All Delegum toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources