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

Construction activity by municipality (barometer)

construction_barometer

Read-onlyIdempotent

Use this when the question is how much is being built in Portuguese municipalities. It gives our monthly count of building-works cases entering licensing, where we collect them, and INE's yearly licensed buildings and new dwellings for all 308. Do not use it for other figures (municipality_stats). Without municipality it returns every municipality we collect and the panel index. measure and granularity change only our own series. A case is not a granted licence or a building.

Input Schema

Name	Required	Description	Default
`measure`	No	Kind of works counted in our own series: all works, new buildings, or alterations and extensions	total_works
`language`	No	Language of the page links and labels; the text summary and field names stay English. uk is accepted as ua.	en
`granularity`	No	Period of our own series; the INE series is yearly either way	month
`municipality`	No	Optional. 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. Omit for the summary of every municipality we collect

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 19, 2026

addedInput schema / properties / granularity / default
```
Added value: +"month"
```

changedInput schema / properties / granularity / description

Previous value: -"Period of our own series. Default: month"New value: +"Period of our own series; the INE series is yearly either way"

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."

addedInput schema / properties / measure / default
```
Added value: +"total_works"
```

changedInput schema / properties / measure / description

Previous value: -"Kind of works: total_works (default), new_build, alter_extend"New value: +"Kind of works counted in our own series: all works, new buildings, or alterations and extensions"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "description": "Without municipality: every municipality we collect, and the index.",
+      "properties": {
+        "attribution": {
+          "type": "object"
+        },
+        "caveat": {
+          "type": "string"
+        },
+        "language": {
+          "type": "string"
+        },
+        "measure": {
+          "type": "string"
+        },
+        "method_url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "municipalities": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "panel_index": {
+          "type": "object"
+        },
+        "snapshot": {
+          "description": "Date, YYYY-MM-DD, or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "window": {
+          "type": "object"
+        }
+      },
+      "required": [
+        "language",
+        "measure",
+        "snapshot",
+        "window",
+        "municipalities",
+        "panel_index",
+        "caveat",
+        "url",
+        "method_url",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    {
+      "description": "With municipality: our series (if collected) and INE's yearly series.",
+      "properties": {
+        "attribution": {
+          "type": "object"
+        },
+        "caveat": {
+          "type": "string"
+        },
+        "covered_municipalities": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "granularity": {
+          "type": "string"
+        },
+        "in_own_series": {
+          "type": "boolean"
+        },
+        "ine_official": {
+          "type": "object"
+        },
+        "language": {
+          "type": "string"
+        },
+        "measure": {
+          "type": "string"
+        },
+        "method_url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "municipality": {
+          "type": "object"
+        },
+        "municipality_url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "own_series": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "snapshot": {
+          "description": "Date, YYYY-MM-DD, or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "summary": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "language",
+        "municipality",
+        "measure",
+        "granularity",
+        "snapshot",
+        "in_own_series",
+        "own_series",
+        "summary",
+        "ine_official",
+        "covered_municipalities",
+        "caveat",
+        "url",
+        "method_url",
+        "municipality_url",
+        "attribution"
+      ],
+      "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.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds genuine semantic context beyond them: the dual-series nature ('measure and granularity change only our own series'), the fallback to all municipalities plus a panel index, and the caveat that a case is not a granted licence or a building. It does not mention the `ambiguous` error path, though the schema does.

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?

Five tight sentences with the trigger and exclusion front-loaded and no filler. The token-level density (backticked param names, abbreviations) makes it slightly terse to parse but costs nothing semantically.

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?

With an output schema present, the description needn't explain return shapes, and it covers what an agent actually needs: when to call it, what data it returns, what the two series are, and how the counts should be interpreted. The only opaque term, 'panel index', is resolved by the output schema.

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%, so baseline is 3, but the description supplies a cross-parameter relationship not visible in per-parameter docs: only the in-house series responds to `measure` and `granularity`, while the INE series stays yearly. It otherwise restates schema content (omit `municipality` for the full panel).

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-plus-resource ('monthly count of building-works cases entering licensing' plus INE licensed buildings and new dwellings) scoped to Portuguese municipalities. It also distinguishes itself from the sibling `municipality_stats`, so an agent can route 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 Guidelines5/5

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

Opens with an explicit trigger ('Use this when the question is how much is being built...') and an explicit exclusion ('Do not use it for other figures (`municipality_stats`)'), naming the alternative. The omission behavior for `municipality` is also spelled out.

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.