Skip to main content
Glama

Delegum

by com.delegum

calcular_deduccion_maternidad_irpf

Read-only

Calcula la deducción por maternidad en el IRPF (art. 81 LIRPF): 1.200 €/año por hijo menor de 3 años para madres que trabajen por cuenta propia o ajena, más el incremento por gastos de guardería (hasta 1.000 €/año). Aplica el límite por cotizaciones a la Seguridad Social y descuenta el abono anticipado ya cobrado.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hijosYesLista de hijos menores de 3 años
madre_en_activoNo¿La madre está de alta como trabajadora o cobrando prestación contributiva? Por defecto true.
cotizaciones_ss_anualesYesSuma de las cotizaciones de la madre a la Seguridad Social en el año (€) — límite de la deducción base
importe_abono_anticipado_cobradoNoImporte ya cobrado por abono anticipado (modelo 140) en €. Por defecto 0.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, consistent with a calculation. The description adds behavioral details: it applies a limit based on social security contributions and subtracts advanced payments. No contradictions.

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 a single sentence that efficiently packs all key information: purpose, amounts, conditions, and limits. No redundant words, front-loaded with essential details.

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?

The description covers the calculation logic, conditions, and parameter roles. However, it does not explicitly state the return value format (e.g., a number). Given no output schema, a slightly more explicit return type would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions for each parameter. The description adds value by explaining how parameters relate to the calculation (e.g., cotizaciones as limit, gastos guardería as increment). This exceeds the baseline of 3.

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 specifies the verb 'Calcula' and the resource 'deducción por maternidad en el IRPF', along with concrete amounts (1.200€/año, 1.000€/año). It clearly distinguishes from sibling tools, which cover different tax deductions or calculations.

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

Usage Guidelines4/5

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

The description implies when to use this tool (for maternity deduction), provides context on limits (cotizaciones, abono anticipado), but does not explicitly state when not to use or offer alternatives. Among many similar siblings, the specificity is sufficient.

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
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