Expat Living Italy

List Expat Living Italy's articles

list_articles

Read-onlyIdempotent

Dated, sourced reporting on moving to and retiring in Italy, newest first. Filter by topic, by place (a comune's ISTAT code) or by dataset slug. Each entry has its URL, a Markdown URL for the full text, and the places and datasets it cites. Content is free to use provided you credit Expat Living Italy and link to the article.

Input Schema

TableJSON Schema

Name	Required	Description
`place`	No	A comune's 6-digit ISTAT code (or a province sigla / region slug).
`topic`	No	One of: tax, residency-visas, costs-housing, healthcare, places, daily-life, data-method.
`dataset`	No	A dataset slug from GET /datasets.
`include`	No	Pass `archived` to include archived articles, flagged by `status`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`articles`	Yes
`attribution`	Yes

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": {
+    "articles": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "author": {
+            "type": "string"
+          },
+          "datasets": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "coverage": {
+                  "description": "How much of the place set the data covers, as the article states it.",
+                  "type": "string"
+                },
+                "slug": {
+                  "description": "The dataset's slug in GET /datasets, when the page is one of them.",
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                },
+                "vintage": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "title",
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "deck": {
+            "type": "string"
+          },
+          "markdownUrl": {
+            "description": "The whole article as Markdown, with its citation at both ends.",
+            "type": "string"
+          },
+          "places": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "code": {
+                  "description": "ISTAT code for a comune, sigla for a province, slug for a region.",
+                  "type": "string"
+                },
+                "grain": {
+                  "enum": [
+                    "comune",
+                    "province",
+                    "region"
+                  ],
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "grain",
+                "code",
+                "name",
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "published": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "published",
+              "archived"
+            ],
+            "type": "string"
+          },
+          "supersededBy": {
+            "description": "Slug of the newer article that replaces this one.",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topics": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "updated": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "deck",
+          "author",
+          "published",
+          "updated",
+          "status",
+          "topics",
+          "url",
+          "markdownUrl",
+          "places",
+          "datasets"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "attribution": {
+      "additionalProperties": false,
+      "properties": {
+        "citeAs": {
+          "description": "Per article: \"“<title>” by <author>, Expat Living Italy, <date>. <url>\".",
+          "type": "string"
+        },
+        "creditText": {
+          "type": "string"
+        },
+        "license": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        "required": {
+          "const": true,
+          "description": "Credit with a link is the condition of free use (CC BY 4.0).",
+          "type": "boolean"
+        },
+        "requirement": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "required",
+        "license",
+        "creditText",
+        "requirement",
+        "citeAs"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "articles",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedSep 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/no-open-world, so the safety profile is covered. The description adds real value beyond that: newest-first ordering, the shape of each entry (URL, Markdown URL, cited places/datasets), and licensing/attribution terms that an agent must relay to a user.

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?

Three tightly written sentences with zero filler, and the core purpose and ordering are front-loaded before the filtering and licensing details. Every sentence carries information an agent needs.

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?

An output schema exists, so return-value explanation is not required, yet the description still summarizes entry shape and adds licensing context. It is nearly complete, with the only gap being the unmentioned 'include=archived' filter.

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%, so the schema already documents all four parameters, including the enum and the ISTAT-code format. The description restates the topic/place/dataset filters but adds no syntax or format detail, and it omits the 'include=archived' parameter entirely, leaving the baseline 3.

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 (List) plus resource (articles) and narrows scope to 'moving to and retiring in Italy' with explicit ordering ('newest first'). This clearly separates it from the get_article sibling, which returns a single article, without needing to open either schema.

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?

Names the three filtering axes (topic, place, dataset), which implies how to narrow a listing, but never states when to use this versus get_article or the other list_* siblings, and gives no exclusions or prerequisites. Usage is inferable but not spelled out.

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?