Expat Living Italy

List every dataset behind expatliving.it

list_datasets

Read-onlyIdempotent

The catalog: each dataset's source institution, vintage (the period it describes), geographic grain, license, the expatliving.it page that presents it, and whether it is servable (false = still an unverified draft; never quote its values). Use it to say what data exists and where a reader can see it.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`datasets`	Yes
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedOutput schema / properties / attribution / properties / license

Added value: +{
+  "additionalProperties": false,
+  "description": "License of Expat Living Italy's own work only; upstream data keeps its own license, per dataset.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / attribution / required

Previous value: -[
-  "publisher",
-  "url",
-  "citeAs",
-  "request"
-]New value: +[
+  "publisher",
+  "url",
+  "citeAs",
+  "request",
+  "license"
+]

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"
+    },
+    "datasets": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "download": {
+            "description": "The whole dataset as published JSON: a meta block (provenance, unit, grain) and every place's value.",
+            "type": "string"
+          },
+          "extractedOn": {
+            "description": "ISO date this dataset was extracted from the source.",
+            "type": "string"
+          },
+          "grain": {
+            "description": "The geographic level the source publishes at. NUTS 2 and NUTS 3 are Eurostat/OECD statistical regions — close to, but not the same as, Italy's regions and provinces. Never present a coarser-grain value as if it were measured for one comune.",
+            "enum": [
+              "comune",
+              "province",
+              "region",
+              "nuts2",
+              "nuts3",
+              "national"
+            ],
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "license": {
+            "type": "string"
+          },
+          "page": {
+            "description": "The human-readable page for this dataset on expatliving.it — link readers here.",
+            "type": "string"
+          },
+          "servable": {
+            "description": "False while a hand-curated dataset is still \"draft\" (unverified against its legislation). A non-servable dataset returns no values anywhere in this API.",
+            "type": "boolean"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "source": {
+            "description": "The institution to cite, e.g. \"ISTAT\" or \"Eurostat\".",
+            "type": "string"
+          },
+          "sourceUrl": {
+            "description": "Where this dataset was fetched from upstream.",
+            "type": "string"
+          },
+          "vintage": {
+            "description": "The period the data describes, e.g. \"2025H2\", \"2024\" or \"2015–2024\" — not when it was fetched.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "label",
+          "source",
+          "sourceUrl",
+          "vintage",
+          "extractedOn",
+          "license",
+          "grain",
+          "servable"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "datasets",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/closed-world, and the description adds genuine value beyond that: the crucial semantic that servable=false means an unverified draft whose values must never be quoted. That is a behavioral rule an agent could not infer from annotations. It stops short of describing ordering or size of the catalog.

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?

Two sentences, front-loaded with the resource identity, then the field inventory, then the usage cue. The enumerated field list is dense but each item earns its place by defining the payload; slight density cost keeps it from 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-param, read-only inventory with an output schema, the description supplies the one thing structured data can't: the meaning of the servable flag and the prohibition on quoting unverified drafts. Coverage is strong; only catalog size/ordering is unaddressed.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to clarify. The description appropriately spends its words on return-field meaning instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with 'The catalog' and enumerates the exact attributes each dataset carries (institution, vintage, grain, license, page, servability), so an agent knows precisely what this tool returns. It's clearly distinguishable from get_article/get_coverage by being a full inventory, though it never names a sibling to contrast with.

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

Usage Guidelines4/5

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

'Use it to say what data exists and where a reader can see it' gives a concrete task-level trigger. It doesn't state when NOT to use it (e.g., when you already need a single dataset's values or coverage detail), so it falls short of 5.

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?