Metastate · Imóveis em Portugal

Home purchase costs in Portugal / Custos de comprar casa

calcular_custos_compra

Read-only

Calculates the taxes and fees of buying a home in mainland Portugal with the official 2026 rates: IMT transfer tax (primary residence, second home, or under-35 exemption), stamp duty 0.8% and land registry (Casa Pronta). / Calcula IMT, imposto do selo e registo com as tabelas de 2026. Example arguments: {"preco_eur":500000,"finalidade":"habitacao_propria","com_credito":true}

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": {
      "preco_eur": "<preco_eur>"
    },
    "name": "calcular_custos_compra"
  }
}

Input Schema

Name	Required	Description
`preco_eur`	Yes	Purchase price in euros
`finalidade`	No	habitacao_propria = buyer's permanent home; secundaria = second home, investment or rental
`com_credito`	No	true if financed with a mortgage (registry fee is higher)
`comprador_ate_35`	No	true if all buyers are 35 or younger and it is their permanent home (IMT exemption up to 330,539 €)

Output Schema

Name	Required	Description	Default
`fonte`	No
`imt_eur`	No
`total_eur`	No
`registo_eur`	No
`imposto_selo_eur`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds meaningful context beyond that: official 2026 rate tables, mainland-Portugal-only scope, and the 0.8% stamp duty figure. It stops short of stating assumptions/caveats (e.g., that the result is an estimate excluding notary or mortgage arrangement fees).

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?

The purpose is front-loaded and every element (rates year, tax components, jurisdiction) earns its place. The bilingual restatement roughly doubles the length, which is defensible for a Portuguese-market tool but is duplicated content rather than added information.

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?

With an output schema present, return values need not be explained, and the description covers input domain, jurisdiction, and rate version for a simple closed-world calculator. Minor gap: no statement of what the calculation excludes (notary, mortgage arrangement fees) or that results are informational rather than a formal tax assessment.

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 the schema already documents the enum meanings and the 330,539 € under-35 exemption threshold, so the baseline is 3. The example arguments illustrate realistic values and correct enum usage but add no semantic detail about the parameters 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?

States a specific verb ('Calculates') and resource ('taxes and fees of buying a home in mainland Portugal'), and enumerates the exact components (IMT, stamp duty 0.8%, land registry/Casa Pronta) plus the rate vintage (2026). This is clearly a cost calculator, not a listing/valuation/consultant tool, so it is separable from the sibling names without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the purpose (compute purchase costs for a given price and buyer profile) and the jurisdiction limit 'mainland Portugal' implicitly excludes islands, but there is no explicit when-to-use/when-not or comparison against alternatives such as consultar_precos_mercado or pedir_avaliacao. The embedded example call partially compensates by showing a canonical invocation.

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

All Metastate · Imóveis em Portugal 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?