Mirabello Immigration Intelligence

Real-Estate Law for Foreign Buyers

get_property_law

Read-onlyIdempotent

REAL-ESTATE LAW FOR FOREIGN BUYERS in a jurisdiction: whether foreigners may own freehold (unrestricted / restricted zones / leasehold-only / approval required / prohibited), restricted categories (border, agricultural, coastal), approval regimes (e.g. Lex Koller, FIRB), which ownership vehicles a foreigner may lawfully use (direct / local company / foreign company / trust / foundation), purchase taxes and foreign-buyer surcharges, holding taxes on non-resident owners, rental restrictions, repatriation of proceeds, golden-visa linkage and inheritance by foreign heirs. Federal states (US, CH, AU, CA, AE) are flagged subnational: no single country-wide answer is inferred. The law behind a purchase, not listings. Pass cc for one jurisdiction; omit for the covered list. Rules change without notice; conveyancing runs via licensed local professionals. Information, not legal, tax or investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_property_law"
  }
}

Input Schema

Name	Required	Description	Default
`cc`	No	ISO alpha-2 country code, e.g. CH, AE, PT

Output Schema

Name	Required	Description	Default
`error`	No
`terms`	No
`source`	No
`book_url`	No
`provider`	No
`disclaimer`	No
`data_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

changedOutput schema / description

Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."

removedOutput schema / properties / book_url / description

Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."

removedOutput schema / properties / data_updated / description

Removed value: -"Date the underlying dataset was last updated."

removedOutput schema / properties / disclaimer / description

Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."

removedOutput schema / properties / error / description

Removed value: -"Present only when the request could not be fulfilled."

removedOutput schema / properties / provider / description
```
Removed value: -"Always \"Mirabello Consultancy\"."
```

removedOutput schema / properties / source / description

Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."

removedOutput schema / properties / terms / description

Removed value: -"Acceptable-use and information-not-advice terms."

Changed3 schema fields changedOct 8, 2026

removedOutput schema / properties / book_a_consultation

Removed value: -{
-  "description": "URL to book a Mirabello consultation.",
-  "type": "string"
-}

addedOutput schema / properties / book_url

Added value: +{
+  "description": "Link to request a consultation with a Mirabello specialist, for a personal case.",
+  "type": "string"
+}

changedOutput schema / properties / source / description

Previous value: -"Attribution for the data."New value: +"Attribution for the data, when it is not Mirabello Consultancy itself."

AddedAug 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and a closed-world dataset, so the safety profile is covered. The description adds genuinely non-structured caveats: rules change without notice, subnational flagging for US/CH/AU/CA/AE, professional-conveyancing requirement, and an advice disclaimer — useful behavioral context an agent can't get from the annotations.

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?

Purpose and scope are front-loaded, and invocation mechanics plus the disclaimer land at the end. The long parenthetical coverage list is dense but each item is a legitimate retrieval facet; only the disclaimer tail could be tightened.

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?

Output schema exists, so return values need no explanation, and annotations cover safety. Scope, subnational caveat, optional-parameter behavior, and the non-advice framing make it callable as-is; only the missing hand-off to overlapping inheritance/withholding siblings leaves a small gap.

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% and the single cc parameter is already documented as ISO alpha-2. The description still adds semantics the schema lacks: the parameter is optional and omitting it returns the covered-jurisdiction list, which changes the shape of the call's outcome.

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?

Names a specific resource (real-estate law for foreign buyers) and enumerates exactly what facets it returns: freehold rules, restricted zones, approval regimes, ownership vehicles, taxes, repatriation, inheritance. Crucially it differentiates from the sibling listing tools with 'The law behind a purchase, not listings,' so an agent can separate it from get_property/search_properties 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 Guidelines4/5

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

Gives concrete invocation guidance: 'Pass cc for one jurisdiction; omit for the covered list,' and warns that federal states yield no single country-wide answer. It lacks explicit routing to adjacent siblings (forced_heirship_risk, succession_conflict_map, withholding_map) whose topics it partially claims, so the when-not is only partial.

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

All Mirabello Immigration Intelligence 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.