Expat Living Italy

Does a comune meet a regime's geographic criteria?

check_tax_eligibility

Read-onlyIdempotent

For one regime slug (from list_tax_regimes) and one 6-digit ISTAT code (from search_comuni): qualifies, does_not_qualify or not_assessable, with a one-sentence reason to quote. not_assessable is never a no. This is about the place only; say so, and never present it as whether a person qualifies or as tax advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	A regime slug from /tax/regimes, e.g. "regime-7-percent-pensioners".
`comune`	Yes	6-digit ISTAT comune code. Find it with /comuni?q=.

Output Schema

TableJSON Schema

Name	Required	Description
`place`	Yes
`reason`	Yes	One sentence on why, safe to quote.
`regime`	Yes
`headroom`	No	Residents between this comune and the ceiling, when it qualifies.
`disclaimer`	Yes
`population`	Yes
`attribution`	Yes
`maxPopulation`	No
`placesNotPeople`	Yes
`ruleIsIncomplete`	Yes
`geographicEligibility`	Yes	qualifies: the comune meets the regime's verified geographic criteria. does_not_qualify: it doesn't, and the rule has no unverified route that could admit it. not_assessable: no geographic answer can be given (see reason).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attribution": {
+      "additionalProperties": false,
+      "properties": {
+        "citeAs": {
+          "description": "A ready-made citation line.",
+          "type": "string"
+        },
+        "page": {
+          "description": "The expatliving.it page these figures come from — link it when you quote them.",
+          "type": "string"
+        },
+        "publisher": {
+          "type": "string"
+        },
+        "request": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "publisher",
+        "url",
+        "citeAs",
+        "request"
+      ],
+      "type": "object"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "geographicEligibility": {
+      "description": "qualifies: the comune meets the regime's verified geographic criteria. does_not_qualify: it doesn't, and the rule has no unverified route that could admit it. not_assessable: no geographic answer can be given (see reason).",
+      "enum": [
+        "qualifies",
+        "does_not_qualify",
+        "not_assessable"
+      ],
+      "type": "string"
+    },
+    "headroom": {
+      "description": "Residents between this comune and the ceiling, when it qualifies.",
+      "type": "number"
+    },
+    "maxPopulation": {
+      "type": "number"
+    },
+    "place": {
+      "additionalProperties": false,
+      "properties": {
+        "istatCode": {
+          "description": "6-digit ISTAT comune code, e.g. 075029.",
+          "type": "string"
+        },
+        "lat": {
+          "type": "number"
+        },
+        "lng": {
+          "type": "number"
+        },
+        "name": {
+          "type": "string"
+        },
+        "page": {
+          "description": "This comune's profile page on expatliving.it — link it when you quote any figure below.",
+          "type": "string"
+        },
+        "province": {
+          "type": "string"
+        },
+        "provinceCode": {
+          "type": "string"
+        },
+        "provinceSlug": {
+          "type": "string"
+        },
+        "region": {
+          "type": "string"
+        },
+        "regionSlug": {
+          "type": "string"
+        },
+        "slug": {
+          "description": "Stable URL slug for /data/comune/{slug} — never changes, even if a comune merges.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "istatCode",
+        "slug",
+        "name",
+        "province",
+        "provinceCode",
+        "provinceSlug",
+        "region",
+        "regionSlug",
+        "lat",
+        "lng",
+        "page"
+      ],
+      "type": "object"
+    },
+    "placesNotPeople": {
+      "const": true,
+      "type": "boolean"
+    },
+    "population": {
+      "additionalProperties": false,
+      "properties": {
+        "coverage": {
+          "additionalProperties": false,
+          "description": "How many of Italy's places this dataset covers at all, e.g. 7587 of 7894 comuni.",
+          "properties": {
+            "in": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            "of": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "in",
+            "of"
+          ],
+          "type": "object"
+        },
+        "extractedOn": {
+          "description": "ISO date this value was extracted from the source.",
+          "type": "string"
+        },
+        "license": {
+          "type": "string"
+        },
+        "method": {
+          "description": "URL to the methodology page for this dataset.",
+          "type": "string"
+        },
+        "reason": {
+          "description": "Present only when value is null: why this place has no figure.",
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "unit": {
+          "type": "string"
+        },
+        "value": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "vintage": {
+          "description": "The period the value describes, e.g. \"2025H2\" or \"2025\" — not when it was fetched.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "value",
+        "unit",
+        "source",
+        "vintage",
+        "extractedOn",
+        "method",
+        "license"
+      ],
+      "type": "object"
+    },
+    "reason": {
+      "description": "One sentence on why, safe to quote.",
+      "type": "string"
+    },
+    "regime": {
+      "additionalProperties": false,
+      "properties": {
+        "criteria": {
+          "description": "geographic: some comuni qualify and others don't. person: turns on who you are, not where you live; no per-comune answer exists.",
+          "enum": [
+            "geographic",
+            "person"
+          ],
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "page": {
+          "description": "The regime's page on expatliving.it.",
+          "type": "string"
+        },
+        "slug": {
+          "description": "The regime's id, e.g. \"regime-7-percent-pensioners\".",
+          "type": "string"
+        },
+        "status": {
+          "description": "draft: encoded but not yet checked against the legislation. A draft regime's eligibility is never served.",
+          "enum": [
+            "verified",
+            "draft"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "label",
+        "status",
+        "criteria",
+        "page"
+      ],
+      "type": "object"
+    },
+    "ruleIsIncomplete": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "regime",
+    "place",
+    "geographicEligibility",
+    "reason",
+    "population",
+    "ruleIsIncomplete",
+    "placesNotPeople",
+    "disclaimer",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedOct 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety is covered. The description adds interpretation context that annotations cannot: the three-valued result set, the instruction to quote the one-sentence reason, and the critical caveat that not_assessable is never a no — which prevents a downstream false negative. It stops short of describing error cases or the shape of the returned object, so a 4 rather than a 5.

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?

Two dense sentences with zero filler: the first covers inputs and outputs, the second covers the framing constraint. The most consequential caveat (not_assessable is never a no) sits early, so nothing important is buried.

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 return structure need not be explained, yet the description still supplies the interpretation rules an agent needs (three-valued outcome, quote the reason, do not over-read not_assessable). Combined with the explicit scope limitation, nothing required to call or correctly report this tool is missing.

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% and both parameters are fully documented there (slug from /tax/regimes, 6-digit ISTAT code found via /comuni?q=). The description restates the same sourcing guidance rather than adding format or constraint detail beyond the schema, so the baseline of 3 applies.

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 verb and resource (checks whether one comune meets one regime's geographic criteria) and enumerates the exact outcome set: qualifies, does_not_qualify, not_assessable. It also names the sibling tools that supply each input (list_tax_regimes, search_comuni), so the agent can place it precisely among the eleven siblings.

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 states the required inputs and their provenance (one slug from list_tax_regimes, one 6-digit ISTAT code from search_comuni), and explicitly bounds when NOT to use its result: it is about the place only, must be described as such, and must never be presented as a person's eligibility or as tax advice. That is explicit when/when-not guidance rather than implied usage.

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

All Expat Living Italy 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.

Resources

Need Help?