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

Explain a Portuguese home-buying term

glossary_lookup

Read-onlyIdempotent

Use this when asked what a Portuguese home-buying or tax term means (CPCV, escritura, VPT…), with where it comes up and the article of law with a link. Do not use it to calculate anything: purchase taxes are imt_calculate, the yearly tax imi_annual_cost. Without term it lists all terms. A term without a translation comes in English; an unknown one is refused with close spellings, if any.

Input Schema

Name	Required	Description	Default
`term`	No	The term: Portuguese or English name, a name in any site language or an abbreviation (CPCV, IMT, VPT, caderneta predial, escritura). Omit to list all terms
`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.

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 answer: the guide or the definition, the text summary and the page links. Field names stay English. uk is accepted as ua."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "description": "Without term: every term.",
+      "properties": {
+        "attribution": {
+          "type": "object"
+        },
+        "count": {
+          "type": "integer"
+        },
+        "language": {
+          "type": "string"
+        },
+        "terms": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "language",
+        "count",
+        "terms",
+        "url",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    {
+      "description": "With term: the definition and the law.",
+      "properties": {
+        "abbreviation": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "attribution": {
+          "type": "object"
+        },
+        "checked_on": {
+          "description": "Date, YYYY-MM-DD",
+          "type": "string"
+        },
+        "definition": {
+          "type": "string"
+        },
+        "en_name": {
+          "type": "string"
+        },
+        "in_practice": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "key": {
+          "type": "string"
+        },
+        "language": {
+          "type": "string"
+        },
+        "language_requested": {
+          "type": "string"
+        },
+        "legal_refs": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "name": {
+          "type": "string"
+        },
+        "pt_name": {
+          "type": "string"
+        },
+        "questions": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "see_also": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "sources": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "updated_on": {
+          "description": "Date, YYYY-MM-DD",
+          "type": "string"
+        },
+        "url": {
+          "description": "Absolute URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "key",
+        "name",
+        "pt_name",
+        "en_name",
+        "abbreviation",
+        "url",
+        "language",
+        "language_requested",
+        "definition",
+        "in_practice",
+        "questions",
+        "legal_refs",
+        "see_also",
+        "updated_on",
+        "checked_on",
+        "sources",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "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.9/5.0

Behavior5/5

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

Annotations already establish a safe read-only, idempotent, non-destructive lookup, but the description adds substantial context beyond them: it returns where terms come up and the relevant article of law with a link, lists all terms when `term` is omitted, falls back to English when no translation exists, and refuses unknown terms with close spellings.

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 compact and front-loaded: usage comes first, exclusions second, and fallback behavior last. Every sentence adds operational value, including sibling alternatives, omission behavior, translation fallback, and unknown-term handling.

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?

An output schema exists, so the description need not document return shape. Given the simple two-parameter lookup with annotations and full schema coverage, the description is complete enough to call correctly and understand edge-case behavior.

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 the baseline is 3, but the description adds behavioral meaning beyond the schema by explaining what happens when `term` is omitted, when a translation is missing, and when a term is unknown. The `language` fallback and refusal behavior are useful additions, though much of the term/listing guidance is already present in 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?

The description states a specific verb-resource action: explaining what a Portuguese home-buying or tax term means, with concrete examples like CPCV, escritura, and VPT. It also distinguishes the tool from sibling calculators by naming imt_calculate and imi_annual_cost, so an agent can identify its role without inspecting other tools.

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 (asked what a term means) and when not to use it (calculation tasks), naming the alternative tools for purchase taxes and yearly tax. It also clarifies edge cases such as omitting `term` to list all terms and behavior for unknown terms.

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.