Delegum

comparar_modulos_vs_directa

Read-only

Calcula el coste anual (IRPF + cuota RETA) de un autónomo en España en Estimación Directa Simplificada (tributa por ingresos menos gastos; la cuota RETA del titular es gasto deducible y se aplica el 5 % de gastos de difícil justificación con su tope) y, si se aporta el rendimiento neto de módulos, también en Estimación Objetiva (módulos), con la reducción general del 5 % de la Orden de módulos vigente, y la diferencia entre ambos costes. NO calcula el rendimiento de módulos: depende de los signos y módulos de cada epígrafe de la Orden; sin él, solo calcula la directa. No recomienda régimen: la diferencia de un año es un dato, no una decisión.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingresos_anuales": "<ingresos_anuales>",
      "gastos_anuales": "<gastos_anuales>",
      "cuota_reta_mensual": "<cuota_reta_mensual>"
    },
    "name": "comparar_modulos_vs_directa"
  }
}

Input Schema

Name	Required	Description
`gastos_anuales`	Yes	Gastos deducibles anuales (€) — solo cuentan en Estimación Directa; también se usan como aproximación a las compras para el límite de exclusión de módulos
`ingresos_anuales`	Yes	Ingresos anuales de la actividad (€)
`cuota_reta_mensual`	Yes	Cuota mensual de autónomo (RETA) en €
`rendimiento_neto_modulos`	No	Rendimiento neto de módulos anual (€): el que resulta de aplicar a la actividad la Orden de módulos vigente (módulos × importe, menos minoraciones por incentivos al empleo y a la inversión, con los índices correctores), ANTES de la reducción general del 5 %. Lo da la gestoría. Si no se aporta, solo se calcula la Estimación Directa.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 1, 2026

removedInput schema / properties / actividad

Removed value: -{
-  "description": "Tipo de actividad (determina la fórmula de módulos)",
-  "enum": [
-    "bar",
-    "comercio_menor",
-    "transporte",
-    "peluqueria",
-    "taxi"
-  ],
-  "type": "string"
-}

changedInput schema / properties / gastos_anuales / description

Previous value: -"Gastos deducibles anuales (€) — solo cuentan en Estimación Directa"New value: +"Gastos deducibles anuales (€) — solo cuentan en Estimación Directa; también se usan como aproximación a las compras para el límite de exclusión de módulos"

removedInput schema / properties / kwh_anuales

Removed value: -{
-  "description": "Consumo eléctrico anual en kWh (relevante en hostelería). Por defecto 0.",
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / mesas

Removed value: -{
-  "description": "Nº de mesas (bares y restaurantes). Por defecto 0.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / personal_asalariado

Removed value: -{
-  "description": "Nº de trabajadores asalariados. Por defecto 0.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / personal_no_asalariado

Removed value: -{
-  "description": "Nº de personas no asalariadas (titular, familiares colaboradores). Por defecto 0.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / rendimiento_neto_modulos

Added value: +{
+  "description": "Rendimiento neto de módulos anual (€): el que resulta de aplicar a la actividad la Orden de módulos vigente (módulos × importe, menos minoraciones por incentivos al empleo y a la inversión, con los índices correctores), ANTES de la reducción general del 5 %. Lo da la gestoría. Si no se aporta, solo se calcula la Estimación Directa.",
+  "minimum": 0,
+  "type": "number"
+}

removedInput schema / properties / superficie_m2

Removed value: -{
-  "description": "Superficie del local en m². Por defecto 0.",
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / vehiculos

Removed value: -{
-  "description": "Nº de vehículos (transporte/taxi). Por defecto 0.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

changedInput schema / required

Previous value: -[
-  "ingresos_anuales",
-  "gastos_anuales",
-  "cuota_reta_mensual",
-  "actividad"
-]New value: +[
+  "ingresos_anuales",
+  "gastos_anuales",
+  "cuota_reta_mensual"
+]

AddedJul 21, 2026

TDQS

A4.1/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 most behavioral disclosure. It adds substantial context: dependency on external gestoría data, treatment of the RETA quota as deductible, the 5% difficult-justification expense cap, and explicit non-behaviors (does not calculate módulos, does not recommend). It does not describe output format or rounding.

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?

Front-loaded with the core calculation and avoids filler despite dense domain detail. The single long paragraph is justified by the complexity, though minor readability cost remains.

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 complex calculator with full schema coverage but no output schema, the description explains what is computed (both costs and the difference) and the missing-input fallback. It does not spell out the return structure or rounding, but the key result semantics are inferable.

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 baseline is 3. The description largely restates the schema's conditional behavior for rendimiento_neto_modulos and does not add parameter syntax, constraints, or format details beyond it; the gastos approximation note is already present in the schema.

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' and a precise resource: 'coste anual (IRPF + cuota RETA)' for Estimación Directa and, conditionally, módulos. It distinguishes itself from generic siblings by narrowly scoping the comparison and explicitly excluding rendimiento de módulos and regime recommendations.

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?

Provides clear conditions: if rendimiento_neto_modulos is supplied it also calculates módulos, otherwise only directa. It also sets an explicit boundary by stating it does not recommend a regime. It does not name sibling alternatives, so 4 rather than 5.

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

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

Need Help?