Frihet MCP Server

Get Modelo 180 Summary (IRPF Rentals Annual)

get_modelo_180_summary

Read-onlyIdempotent

Retrieve the annual IRPF summary for rental income withholdings (Modelo 180). Get total retentions per tenant, property, and annual aggregate for a given year.

Instructions

Get IRPF annual informative summary for rental income withholdings (Modelo 180, Spain). Returns total retentions per tenant, property, and annual aggregate. Example: period='2025' / Obtiene el resumen anual de retenciones sobre alquileres para el Modelo 180. Devuelve retenciones totales por inquilino, inmueble y agregado anual.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	Year in format YYYY (e.g. '2025') / Ejercicio en formato YYYY

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`model`	No
`months`	No	Months covered by the period (YYYY-MM)
`period`	No	YYYY-QN (303/130) or YYYY (390)
`summary`	No
`deadline`	No
`readonly`	No	Marks the payload as an informational summary, never filed to AEAT
`totalDue`	No
`modelo130`	No
`modelo303`	No
`modelo390`	No
`modeloCode`	No
`totalsByRate`	No
`totalDeductible`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.3Jul 22, 2026
Removedv1.15.2Jul 18, 2026

Changed10 schema fields changedv1.14.5Jul 7, 2026

addedOutput schema / properties / model
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / modelo130

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "gastos": {
+      "type": "number"
+    },
+    "ingresos": {
+      "type": "number"
+    },
+    "pagoFraccionado": {
+      "description": "Pago fraccionado IRPF (20% del rendimiento neto)",
+      "type": "number"
+    },
+    "rendimientoNeto": {
+      "type": "number"
+    },
+    "retencionesSoportadas": {
+      "description": "IRPF withheld by clients on issued invoices",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / modelo303

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "baseDeducible": {
+      "description": "Deductible base (input)",
+      "type": "number"
+    },
+    "baseExenta": {
+      "description": "Base of exempt operations (zero cuota)",
+      "type": "number"
+    },
+    "baseImponible": {
+      "description": "IVA devengado base (operaciones interiores sujetas)",
+      "type": "number"
+    },
+    "baseNoSujetaORC": {
+      "description": "Intra-community / export / reverse-charge base",
+      "type": "number"
+    },
+    "cuotaDeducible": {
+      "description": "Input VAT (cuota deducible)",
+      "type": "number"
+    },
+    "cuotaRepercutida": {
+      "description": "Output VAT (cuota repercutida)",
+      "type": "number"
+    },
+    "outOfScope": {
+      "additionalProperties": {},
+      "description": "IGIC/IPSI totals — outside the 303 self-assessment",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "resultado": {
+      "description": "cuotaRepercutida − cuotaDeducible (+ to pay, − to refund/compensate)",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / modelo390

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "baseDeducible": {
+      "type": "number"
+    },
+    "baseExenta": {
+      "type": "number"
+    },
+    "baseImponible": {
+      "type": "number"
+    },
+    "baseNoSujetaORC": {
+      "type": "number"
+    },
+    "cuotaDeducible": {
+      "type": "number"
+    },
+    "cuotaRepercutida": {
+      "type": "number"
+    },
+    "outOfScope": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "resultadoAnual": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / months

Added value: +{
+  "description": "Months covered by the period (YYYY-MM)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / period / description
```
Added value: +"YYYY-QN (303/130) or YYYY (390)"
```

addedOutput schema / properties / readonly

Added value: +{
+  "const": true,
+  "description": "Marks the payload as an informational summary, never filed to AEAT",
+  "type": "boolean"
+}

addedOutput schema / properties / summary

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "clientCount": {
+      "type": "number"
+    },
+    "expenseCount": {
+      "type": "number"
+    },
+    "invoiceCount": {
+      "type": "number"
+    },
+    "totalExpenses": {
+      "type": "number"
+    },
+    "totalRevenue": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / required
```
Removed value: -[
-  "modeloCode"
-]
```

Addedv1.13.1Jun 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description's role is lighter. It adds value by describing what data is returned (retentions per tenant, property, annual aggregate) and includes an example, fully aligning with annotations.

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 concise (two sentences plus an example) and front-loaded with the essential purpose. Every sentence contributes meaning, and the bilingual format is a minor addition that does not harm conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter, full annotation coverage, and an output schema, the description provides complete context: what the tool does, what it returns, and an example. No gaps remain.

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% and describes the parameter 'period' as 'Year in format YYYY'. The description adds an example ('period='2025'') but does not provide significant additional semantics beyond the schema, meeting the baseline.

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 it retrieves the IRPF annual summary for rental income withholdings (Modelo 180 in Spain), specifying it returns retentions per tenant, property, and annual aggregate. This distinguishes it from sibling tools like get_modelo_130_summary which target different tax forms.

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 indicates this tool is for rental income withholdings under Modelo 180, providing clear context. However, it does not explicitly state when to use it versus other modelo summaries, though the naming and context make the distinction apparent.

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

Deploy Server