Delegum

calcular_legitimas

Read-only

Calcula la herencia forzosa (legítima) que corresponde por ley a los descendientes según el régimen civil aplicable en España (Derecho Común, Cataluña, Aragón, Galicia, Baleares, País Vasco o Navarra). Devuelve la legítima total, la parte por hijo, el tercio de mejora, la parte de libre disposición y el derecho del cónyuge viudo. No calcula el Impuesto de Sucesiones (para eso usa "calcular_sucesiones").

Input Schema

TableJSON Schema

Name	Required	Description
`regimen`	Yes	Régimen civil aplicable. "comun" = Código Civil (mayoría de CCAA); el resto son derechos forales.
`num_hijos`	Yes	Número de hijos o descendientes
`tiene_conyuge`	No	¿Hay cónyuge viudo con derecho a usufructo/cuota vidual? Por defecto false.
`patrimonio_neto`	Yes	Patrimonio neto hereditario (caudal relicto) en euros

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds that the tool returns computed values (total legitima, share per child, etc.) and does not modify data. It does not elaborate on edge cases but provides sufficient behavioral context.

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?

The description is two sentences, front-loaded with the main purpose, lists outputs, and includes a cross-reference to an alternative. Every sentence adds value with no fluff.

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?

Given the tool's complexity (multiple civil regimes, no output schema), the description is fairly complete: it covers what is calculated and what is returned. However, it lacks details on regime-specific differences or edge cases like zero children.

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%, so baseline is 3. The description does not add extra meaning to parameters beyond what the schema already provides, though it lists return values that indirectly relate to parameters.

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 explicitly states the tool calculates the forced heirship (legítima) for descendants under various Spanish civil regimes, directly stating its specific function and distinguishing it from siblings like 'calcular_sucesiones'.

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?

The description clearly states when to use this tool (for calculating legitima) and explicitly directs users away from using it for inheritance tax, naming the alternative tool 'calcular_sucesiones'.

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

All Delegum tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.

Naming Consistency5/5

All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.

Tool Count3/5

49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.

Completeness4/5

The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).

Resources

Need Help?