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

Key figures for one Portuguese municipality

municipality_stats

Read-onlyIdempotent

Use this when the key figures of one of Portugal's 308 municipalities are needed, each with its source and date. They are the IMI rate and history, INE sale price per m² (actual sales), purchasing power, population, licensed dwellings, building cases, new builds. Do not use it to compare places (compare_municipalities), inside a city (where_to_live) or for monthly building (construction_barometer). A figure that is not published is null, not estimated. A name matching two municipalities is refused with candidates.

Input Schema

Name	Required	Description	Default
`language`	No	Language of the page links and labels; the text summary and field names stay English. uk is accepted as ua.	en
`municipality`	Yes	Municipality name in any case, accents optional (Porto, Lisboa, Vila Nova de Gaia, Matosinhos; Lisbon and Oporto are accepted) or its four-digit code (1312). Close spellings are found; two matches return an `ambiguous` error with candidates

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "properties": {
-      "attribution": {
-        "type": "object"
-      },
-      "construction_barometer": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "imi": {
-        "type": "object"
-      },
-      "language": {
-        "type": "string"
-      },
-      "licensed_buildings_all_works": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "licensed_new_buildings": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "licensed_new_dwellings": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "municipal_cases": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "municipality": {
-        "type": "object"
-      },
-      "new_builds": {
-        "type": "object"
-      },
-      "population": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "purchasing_power": {
-        "description": "Index, Portugal = 100",
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "sale_prices": {
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "url": {
-        "description": "Absolute URL or null",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "where_to_live": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "municipality",
-      "url",
-      "imi",
-      "sale_prices",
-      "purchasing_power",
-      "population",
-      "licensed_new_dwellings",
-      "licensed_new_buildings",
-      "licensed_buildings_all_works",
-      "municipal_cases",
-      "construction_barometer",
-      "new_builds",
-      "where_to_live",
-      "attribution",
-      "language"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "candidates": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "suggestions": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "error",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "affordability": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "attribution": {
+        "type": "object"
+      },
+      "construction_barometer": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "imi": {
+        "type": "object"
+      },
+      "language": {
+        "type": "string"
+      },
+      "licensed_buildings_all_works": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "licensed_new_buildings": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "licensed_new_dwellings": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "municipal_cases": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "municipality": {
+        "type": "object"
+      },
+      "new_builds": {
+        "type": "object"
+      },
+      "population": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "purchasing_power": {
+        "description": "Index, Portugal = 100",
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "sale_prices": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "url": {
+        "description": "Absolute URL or null",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "where_to_live": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "municipality",
+      "url",
+      "imi",
+      "sale_prices",
+      "purchasing_power",
+      "population",
+      "licensed_new_dwellings",
+      "licensed_new_buildings",
+      "licensed_buildings_all_works",
+      "municipal_cases",
+      "construction_barometer",
+      "new_builds",
+      "where_to_live",
+      "attribution",
+      "language"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "candidates": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "suggestions": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "error",
+      "message"
+    ],
+    "type": "object"
+  }
+]

Changed2 schema fields changedOct 19, 2026

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 page links and labels; the text summary and field names stay English. uk is accepted as ua."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "attribution": {
+          "type": "object"
+        },
+        "construction_barometer": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "imi": {
+          "type": "object"
+        },
+        "language": {
+          "type": "string"
+        },
+        "licensed_buildings_all_works": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "licensed_new_buildings": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "licensed_new_dwellings": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "municipal_cases": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "municipality": {
+          "type": "object"
+        },
+        "new_builds": {
+          "type": "object"
+        },
+        "population": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "purchasing_power": {
+          "description": "Index, Portugal = 100",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "sale_prices": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "where_to_live": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "municipality",
+        "url",
+        "imi",
+        "sale_prices",
+        "purchasing_power",
+        "population",
+        "licensed_new_dwellings",
+        "licensed_new_buildings",
+        "licensed_buildings_all_works",
+        "municipal_cases",
+        "construction_barometer",
+        "new_builds",
+        "where_to_live",
+        "attribution",
+        "language"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "candidates": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "suggestions": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "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.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: every figure carries its source and date, unpublished figures return null rather than estimates, and ambiguous names are refused with candidates. It omits nothing critical, though response shape is left to the output 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?

Front-loaded with the when-to-use clause, followed by the field list, then the exclusions in a compact parenthetical list. Four sentences, no filler, each carrying distinct information.

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?

Output schema exists so return values need no explanation, annotations cover the safety profile, and parameters are fully documented. The description fills the remaining gaps an agent needs: field inventory, null-not-estimated policy, and error behavior on ambiguous names.

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 both parameters are fully documented in the schema, so the baseline is 3. The description adds marginal but genuine meaning by restating the ambiguity refusal behavior (candidates returned) and the fact field labels stay English regardless of the language parameter is schema-side. Slight edge over 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?

States a specific verb and resource (key figures for one Portuguese municipality) and enumerates the exact figures returned (IMI rate, INE sale price per m², purchasing power, population, etc.). That enumeration makes it immediately distinguishable from siblings like imi_rate or municipality_housing_pipeline.

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?

Explicit 'Use this when...' plus an explicit 'Do not use it to compare places (compare_municipalities), inside a city (where_to_live) or for monthly building (construction_barometer)'. Each exclusion names the sibling that covers that case, leaving nothing to inference.

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.