flatin.pt — Portuguese homes: taxes, construction, new-builds

Where to live in a Portuguese city, area by area

where_to_live

Read-onlyIdempotent

Use this when the person is choosing a neighbourhood: a flatin.pt city guide's verdict area by area, with the reason, who each area suits and the sources. Do not use it for one municipality's figures (municipality_stats) or for new homes there (search_newbuilds). Without city it lists the cities and regions that have a guide. profile narrows the areas but never hides the ones we advise against. Noise and safety come as dated, sourced facts: a place's reputation, never a claim about its people. Show the guide's link to the user.

Input Schema

Name	Required	Description	Default
`city`	No	City or region with a guide, in any site language (Porto, Lisbon, Lisboa, Greater Porto, Algarve, Coimbra) or a municipality inside a guide (Gaia, Cascais, Faro). Omit to list the guides
`include`	No	Parts of the guide to return; all returns every section
`profile`	No	Keep the areas that suit this profile; profile never removes the areas we advise against
`verdict`	No	Keep only areas with this verdict: live (good to live), depends (depends on you), avoid (we advise against)
`language`	No	Language of the answer: the guide or the definition, the text summary and the page links. Field names stay English. uk is accepted as ua.	en

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / include / default

Added value: +[
+  "areas",
+  "noise",
+  "safety"
+]

changedInput schema / properties / include / description

Previous value: -"Parts of the guide to return. Default: areas, noise, safety"New value: +"Parts of the guide to return; all returns every section"

changedInput schema / properties / language / description

Previous value: -"Language of the site content in the answer (verdicts, definitions, labels) and of the page links: pt, en, ru, ua (or uk), de, fr, nl. Field names and the summary stay English. Default: en"New value: +"Language of the answer: the guide or the definition, the text summary and the page links. Field names stay English. uk is accepted as ua."

changedInput schema / properties / profile / description

Previous value: -"Keep the areas that suit this profile; areas we advise against are always kept"New value: +"Keep the areas that suit this profile; profile never removes the areas we advise against"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "description": "Without city: the guides that exist.",
+      "properties": {
+        "attribution": {
+          "type": "object"
+        },
+        "guides": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "language": {
+          "type": "string"
+        },
+        "profiles": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "language",
+        "guides",
+        "profiles",
+        "url",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    {
+      "description": "With city: one guide's verdict area by area.",
+      "properties": {
+        "areas": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attribution": {
+          "type": "object"
+        },
+        "filters": {
+          "type": "object"
+        },
+        "guide": {
+          "type": "object"
+        },
+        "hub_url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "language": {
+          "type": "string"
+        },
+        "language_requested": {
+          "type": "string"
+        },
+        "lede": {
+          "type": "string"
+        },
+        "published_on": {
+          "description": "Date, YYYY-MM-DD",
+          "type": "string"
+        },
+        "sections": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "sources": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "title": {
+          "type": "string"
+        },
+        "updated_on": {
+          "description": "Date, YYYY-MM-DD",
+          "type": "string"
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "verdict_scale": {
+          "type": "object"
+        }
+      },
+      "required": [
+        "guide",
+        "language",
+        "language_requested",
+        "title",
+        "lede",
+        "filters",
+        "verdict_scale",
+        "areas",
+        "sections",
+        "url",
+        "hub_url",
+        "published_on",
+        "updated_on",
+        "sources",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "error": {
+          "type": "string"
+        },
+        "guides": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error",
+        "message"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Success, or a refusal with an error code. Units: *_cents euro cents, *_eur euros, *_eur_m2 euros per m², *_pct and percent in percent.",
+  "type": "object"
+}

AddedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish the read-only, non-destructive, idempotent profile. The description adds useful behavioral context beyond that: listing cities when `city` is omitted, preserving advised-against areas under `profile`, treating noise and safety as dated sourced facts rather than claims about people, and instructing the agent to show the guide link. It does not add much about return shape, but the output schema exists.

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 dense but front-loaded: it opens with the use case, immediately states exclusions and alternatives, then covers edge cases and behavioral nuances. Every sentence contributes routing or behavioral guidance.

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?

Given the rich annotations, full schema coverage, and output schema, the description provides everything an agent needs: purpose, alternatives, edge-case behavior, profile semantics, sourcing stance, and link handling. No material gap remains for correct selection or invocation.

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 schema already documents all five parameters thoroughly. The description reinforces a few behaviors such as the omitted-`city` fallback and `profile` preservation, but does not add meaning beyond what the schema already states.

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 names a specific decision context (choosing a neighbourhood) and a concrete resource (flatin.pt city guide's area-by-area verdicts, reasons, suitability, and sources). It also distinguishes the tool from `municipality_stats` and `search_newbuilds`, so an agent can identify its role without opening sibling schemas.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool and when not to use it, naming the two sibling alternatives for the excluded cases. It also explains the no-`city` fallback, giving an agent clear routing guidance.

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

All flatin.pt — Portuguese homes: taxes, construction, new-builds 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.