Piazza in Festa

Comuni coperti, con il loro identificativo

comuni_coperti

Read-onlyIdempotent

L'elenco dei comuni per cui abbiamo eventi, con il loro identificativo. Serve a trovare l'identificativo giusto prima di chiamare cerca_eventi.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`regione`	No	Limita a una regione.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`comuni`	Yes	Al massimo 500 comuni: senza il filtro regione la lista nazionale sarebbe di migliaia di righe.
`totale`	Yes	Quanti comuni hanno eventi in tutto, anche oltre quelli elencati qui.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "comuni": {
+      "description": "Al massimo 500 comuni: senza il filtro regione la lista nazionale sarebbe di migliaia di righe.",
+      "items": {
+        "properties": {
+          "comune": {
+            "description": "Identificativo da passare al filtro comune.",
+            "type": "string"
+          },
+          "comune_nome": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "eventi": {
+            "description": "Quanti eventi ha in catalogo.",
+            "type": "integer"
+          },
+          "provincia": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "regione": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "comune",
+          "eventi"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totale": {
+      "description": "Quanti comuni hanno eventi in tutto, anche oltre quelli elencati qui.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "totale",
+    "comuni"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful scope information: the list contains only municipalities we have events for and includes identifiers. It does not over-explain, but it also does not add much behavioral depth 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?

Two short sentences with no filler. The first states what the tool returns, and the second explains why it mattersaren't used, each earning its place.

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?

The tool is a simple read-only list with one optional filter, and an output schema exists. The description gives enough context for an agent to know when and why to call it, and nothing important 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?

The schema documents the single optional parameter `regione` with 100% coverage. The description provides no additional meaning beyond what the schema already states, so the baseline of 3 is appropriate.

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 clearly states the tool returns the list of municipalities that have events, along with their identifierschers. It explicitly frames the purpose as a lookup step before calling cerca_eventi, which distinguishes it from the sibling event-oriented tools even without naming them.

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 description says this tool is meant to be used before calling cerca_eventi, to find the correct identifier. This gives a clear contextual trigger, though it does not state explicit conditions for when not to use it. Given the tool's simple role, the guidance is adequate.

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

All Piazza in Festa tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?