Skip to main content
Glama

CasitaTax

Estimate Modelo 210

estimate_modelo_210
Read-onlyIdempotent

Use this when a non-resident owner of a home in Spain asks how much Modelo 210 (Spanish non-resident income tax on the property) they owe for a tax year. Works out each owner's tax on the imputed income of the days the home wasn't let and on the rent, as CasitaTax's simulator does, and returns the method, the sources and a link that opens the simulator with the same answers.

Input Schema

NameRequiredDescriptionDefault
rentNoFor rented or part: the rent received for the whole home during the tax year, in euros, before expenses.
ownersNoNumber of owners, 1 to 6, with equal shares. Default 1.
revisedNoWhether the town's cadastral values were revised collectively and in force since the year the rules require (town_cadastral_data tells). Default unknown: the tax is then a range.
expensesNoFor rented or part, owners resident in the EU or the EEA: the deductible expenses of the rented period for the whole home, in euros. Ignored for others, who are taxed on the gross rent.
languageNoLanguage of the CasitaTax pages linked in the answer: da, de, en, es, fr, nl, no, fi or sv. Default en.
tax_yearNoTax year (the year the income relates to). Default: the latest year whose rules are final.
occupancyYesunrented: not let during the tax year (own use, empty); rented: let all year; part: let part of the year.
residenceYesWhere the owners live for tax purposes: eu (a country of the EU, or Iceland, Norway, Liechtenstein), uk (United Kingdom), other (anywhere else). One value for all the owners.
rented_daysNoFor occupancy part: the number of days the home was let during the tax year.
shares_percentNoEach owner's share of the home in percent, when the shares differ (e.g. [60, 40]); they add up to 100. Replaces owners.
cadastral_valueYesThe home's valor catastral in euros, for the tax year: on the IBI receipt (total, not just the land or the building).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds real value by disclosing the return shape (method, sources, a simulator link carrying the same answers) and the imputed-income-plus-rent computation. It doesn't mention that the result becomes a range when cadastral revision status is unknown — that caveat lives only in the schema.

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?

Two sentences, front-loaded with the 'use this when' trigger, followed by what it computes and returns. No filler, no restatement of the title.

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?

Despite 11 parameters and no output schema, the description covers both the input situation and what comes back (method, sources, deep link), so an agent can decide and call correctly. Remaining detail is fully carried by a 100%-covered schema.

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% and each of the 11 parameters is documented in-schema with enums and defaults, so baseline 3 applies. The description only echoes the occupancy/rent split conceptually and adds no format, default, or interdependency detail beyond 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?

It names a specific verb (estimate the tax owed) and resource (Modelo 210 non-resident income tax), and the scope is narrow enough to separate it from modelo_210_deadlines (dates) and town_cadastral_data (cadastral values). It also states the computation model — imputed income for unlet days plus rent, split per owner.

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 opening clause gives an explicit trigger condition: a non-resident owner of a Spanish home asking how much Modelo 210 they owe for a given year. No when-not cases or sibling alternatives are named, though the schema's reference to town_cadastral_data hints at the pairing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources