Skip to main content
Glama

Delegum

by com.delegum
OverviewDiscussionsAdmin

calcular_sucesiones

Read-only

Calcula el Impuesto de Sucesiones (ISD) de un heredero individual con reducciones y bonificaciones autonómicas. Para la consulta general de herencia usa "consulta_herencia". NO calcula la reducción por empresa familiar (empresa individual, negocio profesional o participaciones en entidades), ni la estatal ni las autonómicas: exige valorar la empresa y comprobar requisitos que solo puede verificar un asesor fiscal. Si lo que se transmite incluye una empresa o participaciones, NO presentes la cuota como estimación del caso: dile al usuario que la herramienta no cubre la empresa familiar y que consulte a un asesor fiscal. IMPORTANTE: si el usuario está comparando donar en vida vs esperar a la herencia de un inmueble, NO uses esta herramienta suelta ni la sumes a mano con otras: usa directamente "comparar_donacion_vs_herencia", que integra ISD, IRPF del donante y plusvalía municipal en una sola respuesta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccaaYesComunidad autónoma del fallecido
seguro_vidaNoImporte de seguro de vida recibido
discapacidadNoGrado de discapacidad. Por defecto "0".
edad_herederoNoEdad del heredero. Necesaria si es del Grupo III (colateral: hermanos, sobrinos, tíos) y hay vivienda habitual: el art. 20.2.c LISD le exige 65 años o más. También activa la reducción adicional del menor de 21 años en descendientes.
valor_herenciaYesValor neto recibido por el heredero en euros
grupo_parentescoYesGrupo de parentesco. II=HIJO de 21 o más; II-descendiente=nieto/bisnieto de 21 o más (en Cataluña reducen distinto: 100.000 € frente a 50.000 €)
vivienda_habitualNoValor de la vivienda habitual heredada (reducción 95%)
convivio_dos_aniosNoSi el heredero convivió con el fallecido los dos años anteriores. Solo se le exige al Grupo III (colateral) para la reducción por vivienda habitual (art. 20.2.c LISD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / grupo_parentesco / description
      Previous value: -"Grupo de parentesco"New value: +"Grupo de parentesco. II=HIJO de 21 o más; II-descendiente=nieto/bisnieto de 21 o más (en Cataluña reducen distinto: 100.000 € frente a 50.000 €)"
    • changedInput schema / properties / grupo_parentesco / enum
      Previous value: -[
-  "I-conyuge",
-  "I-descendiente",
-  "II",
-  "II-ascendiente",
-  "III",
-  "IV"
-]New value: +[
+  "I-conyuge",
+  "I-descendiente",
+  "II",
+  "II-descendiente",
+  "II-ascendiente",
+  "III",
+  "IV"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / convivio_dos_anios
      Added value: +{
+  "description": "Si el heredero convivió con el fallecido los dos años anteriores. Solo se le exige al Grupo III (colateral) para la reducción por vivienda habitual (art. 20.2.c LISD).",
+  "type": "boolean"
+}
    • addedInput schema / properties / edad_heredero
      Added value: +{
+  "description": "Edad del heredero. Necesaria si es del Grupo III (colateral: hermanos, sobrinos, tíos) y hay vivienda habitual: el art. 20.2.c LISD le exige 65 años o más. También activa la reducción adicional del menor de 21 años en descendientes.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds significant behavioral context: it discloses that it does not calculate the empresa familiar reduction and provides specific instructions on how to handle such cases (telling the user to consult an asesor). It also clarifies what the tool integrates (ISD only) for the comparison case, making limitations transparent.

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?

Although the description is long, every sentence earns its place: it opens with the core purpose, then gives alternatives, exclusions, and explicit directives for edge cases. It is structured logically, with important warnings clearly highlighted (e.g., empresa familiar and comparar_donacion_vs_herencia). No filler or redundancy.

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 calculator with 8 parameters and no output schema, the description covers the primary usage scenarios, exclusions, and alternative tools. It does not specify the return format, but given the tool is a numerical calculator and the schema covers all input requirements, this is a minor gap. The description is complete enough for an agent to determine correct usage and avoid misuse.

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 description coverage is 100%: all 8 parameters have individual descriptions. The tool description does not add parameter-level details beyond what the schema already provides. It mentions 'reducciones y bonificaciones autonómicas' which relates to the ccaa parameter, but that is already implied by the schema description for that parameter. 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 the tool calculates the Impuesto de Sucesiones (ISD) for an individual heir, including reductions and regional bonuses. It explicitly distinguishes itself from 'consulta_herencia' (general consultation) and 'comparar_donacion_vs_herencia' (comparison), making its specific purpose unambiguous.

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

Usage Guidelines5/5

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

Usage guidance is explicit and thorough. It directs users to 'consulta_herencia' for general inheritance queries, and explicitly says NOT to use this tool for comparing donation vs inheritance but to use 'comparar_donacion_vs_herencia' instead. It also warns against presenting results when empresa familiar is involved and instructs to refer to an asesor fiscal. Multiple exclusion criteria and alternatives are provided.

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