Skip to main content
Glama
Sign In

Expat Living Italy

by it.expatliving
OverviewDiscussionsAdmin

Find a comune by name

search_comuni
Read-onlyIdempotent

Look up Italian comuni by name (case- and accent-insensitive, partial names work) and get each one's 6-digit ISTAT code, province and region — the code get_comune needs. Returns identifiers only, no figures. Several comuni share a name; check the province before choosing.

Input Schema

NameRequiredDescriptionDefault
qYesA comune name or part of one, accents optional — e.g. "Introdacqua" or "reggio".
limitNoHow many matches to return, 1–25. Default 10.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYesBest matches first: exact name, then names starting with the query, then names containing it. Several Italian comuni share a name — check the province before picking one.
truncatedYesTrue when more comuni matched than `limit` allowed — narrow the query.
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. 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"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "description": "Best matches first: exact name, then names starting with the query, then names containing it. Several Italian comuni share a name — check the province before picking one.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "istatCode": {
+            "description": "6-digit ISTAT comune code — pass this to GET /comuni/{istatCode} or get_comune.",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "page": {
+            "description": "The comune's profile page on expatliving.it.",
+            "type": "string"
+          },
+          "province": {
+            "type": "string"
+          },
+          "provinceCode": {
+            "type": "string"
+          },
+          "region": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "istatCode",
+          "name",
+          "province",
+          "provinceCode",
+          "region",
+          "page"
+        ],
+        "type": "object"
+      },
+      "maxItems": 25,
+      "type": "array"
+    },
+    "truncated": {
+      "description": "True when more comuni matched than `limit` allowed — narrow the query.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "query",
+    "results",
+    "truncated",
+    "attribution"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered; the description usefully adds that matching is case- and accent-insensitive with partial names, that only identifiers are returned (no figures), and that duplicate names are common. That is real context beyond the annotations.

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 short sentences, zero filler, with the core capability and the return payload front-loaded before the caveat. Every clause carries information an agent would otherwise have to guess.

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, yet the description still flags that only identifiers come back, pre-empting an agent expecting numeric data. Combined with the duplicate-name warning and the get_comune handoff, nothing needed to call it correctly 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 coverage is 100%, so both parameters are documented in the schema itself. The description's 'case- and accent-insensitive, partial names work' largely restates the schema's 'accents optional' and 'part of one', and it says nothing about the limit parameter. Baseline 3 applies.

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?

States a specific verb and resource ('Look up Italian comuni by name') and names exactly what comes back: ISTAT code, province, region. It positions itself relative to get_comune as the producer of that code, though it never addresses how it differs from sibling find_comuni.

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?

'the code get_comune needs' gives a clear downstream-use condition, and 'Several comuni share a name; check the province before choosing' is actionable selection guidance. It stops short of explicit when-not-to-use / alternative routing (e.g., versus find_comuni).

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