Skip to main content
Glama

Delegum

by com.delegum
OverviewDiscussionsAdmin

calcular_donaciones

Read-only

Calcula el Impuesto de Donaciones (ISD) en España con la tarifa estatal o catalana, coeficientes por patrimonio y bonificaciones autonómicas. Para donaciones en vida entre familiares. 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 competente: si se dona un inmueble, la comunidad donde está situado (art. 32.2.b Ley 22/2009); en el resto de bienes, la de residencia habitual del donatario, quien recibe (arts. 32.2.c y 28 Ley 22/2009)
discapacidadNoGrado de discapacidad. Por defecto "0".
valor_donacionYesValor de la donación en euros
grupo_parentescoYesGrupo de parentesco
escritura_publicaNoSi se formaliza en escritura pública (afecta a algunas CCAA). Por defecto true.
patrimonio_preexistenteNoPatrimonio preexistente del donatario en euros. Fija el coeficiente multiplicador (art. 22.2 LISD) con la corrección del salto de tramo. Por defecto 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ccaa / description
      Previous value: -"Comunidad autónoma del donatario (quien recibe)"New value: +"Comunidad autónoma competente: si se dona un inmueble, la comunidad donde está situado (art. 32.2.b Ley 22/2009); en el resto de bienes, la de residencia habitual del donatario, quien recibe (arts. 32.2.c y 28 Ley 22/2009)"
  2. Changed1 schema field changed
    • addedInput schema / properties / patrimonio_preexistente
      Added value: +{
+  "description": "Patrimonio preexistente del donatario en euros. Fija el coeficiente multiplicador (art. 22.2 LISD) con la corrección del salto de tramo. Por defecto 0.",
+  "minimum": 0,
+  "type": "number"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, but the description adds real behavioral context: the calculation method (state or Catalan tariff, wealth coefficients, regional bonifications) and, importantly, the coverage boundary around empresa familiar and the required fallback message to the user. It does not describe the shape of the returned result, which matters somewhat since no output schema exists.

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?

Well front-loaded: purpose first, then exclusions, then the routing warning in caps. The empresa familiar limitation is stated twice (as an exclusion and again as a fallback instruction), which is mildly redundant, though the repetition targets different agent behaviors (don't compute vs. tell the user).

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 6-parameter tax calculator with no output schema, the description covers scope, limitations, and sibling routing thoroughly. The remaining gap is that it never indicates what the result contains (quota breakdown, applicable tariff, bonification applied), which an agent would need to present results correctly.

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%, so the schema already documents ccaa, grupo_parentesco, patrimonio_preexistente, etc. The description reinforces that patrimonio drives the multiplicador and that ccaa determines the tariff, but adds no syntax or format detail beyond the structured fields — the baseline of 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 ('Calcula el Impuesto de Donaciones (ISD) en España') and immediately scopes it to 'donaciones en vida entre familiares', which separates it from calcular_sucesiones and other tax calculators. An agent can identify the tool's domain without opening the schema.

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?

Explicit when-not rules: excludes the empresa familiar reduction and instructs the agent not to present the quota as an estimate in that case. It also names the alternative sibling ('comparar_donacion_vs_herencia') and the exact scenario that selects it (comparing lifetime gift vs inheritance of a property).

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