Skip to main content
Glama

Expat Living Italy

by it.expatliving
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint=false, idempotentHint), so the bar is lower, yet the description adds real behavioral context: the `servable` flag semantics with the explicit instruction "false = still an unverified draft; never quote its values." That is a meaningful caveat an agent could not derive from structured fields alone. It stops short of 5 only because nothing is said about scope or staleness of the catalog itself.

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, no filler. The field enumeration is somewhat redundant given an output schema exists, but it is compact and the critical servability warning is placed where it will be read. Slightly long but every clause carries information.

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?

With no parameters and a published output schema, the description does not need to explain return values, yet it helpfully surfaces the one field whose semantics matter operationally (servable). The intended use case is stated. Nothing essential to correct invocation is missing, though guidance on pairing it with the coverage/article siblings would make it fully complete.

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?

The tool takes zero parameters, so per the calibration the baseline is 4 and the schema (100% coverage, empty properties) fully carries the parameter burden. The description correctly adds nothing about arguments that do not exist.

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?

The description opens with "The catalog" and enumerates exactly what each entry contains (source institution, vintage, geographic grain, license, presenting page, servability), so the resource is unambiguous. It is distinguishable from the tax/comuni/article siblings, which share no scope with it. The verb is implicit rather than stated, keeping it just short of a 5.

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

Usage Guidelines3/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 an intended use case, so usage is implied rather than absent. However, it offers no when-not conditions, no prerequisites, and no reference to any alternative tool for related questions (e.g. coverage or article lookups). Adequate but thin guidance.

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 toolsInspect
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