dettaglio_eventoTutti i dati di un evento a partire dal suo identificativo, compresi descrizione, informazioni pratiche, organizzatore, se l'ingresso e' libero o a pagamento e il link alla fonte ufficiale.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Identificativo dell'evento, come restituito da cerca_eventi. |
| Name | Required | Description | Default |
|---|---|---|---|
| evento | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "evento": {
+ "properties": {
+ "biglietteria_url": {
+ "description": "Dove si comprano i biglietti, solo se l'atto lo riportava.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "categoria": {
+ "description": "Uno dei valori ammessi per il filtro categoria.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "comune": {
+ "description": "Identificativo del comune, quello che vuole il filtro comune.",
+ "type": "string"
+ },
+ "comune_nome": {
+ "description": "Nome del comune per esteso.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "created_at": {
+ "description": "ISO 8601 UTC.",
+ "type": "string"
+ },
+ "data_fine": {
+ "description": "Formato 'YYYY-MM-DD'. Uguale a data_inizio se l'evento dura un giorno.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "data_inizio": {
+ "description": "Formato 'YYYY-MM-DD'.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date_occorrenze": {
+ "description": "Le singole date quando l'evento non occupa un intervallo pieno, per esempio tre domeniche di fila.",
+ "items": {
+ "type": "string"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "descrizione": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "fonte_permanente_url": {
+ "description": "La nostra copia permanente dell'atto, che non scade.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "fonte_url": {
+ "description": "L'atto sul portale del comune. Puo' sparire quando l'albo ruota.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "description": "Identificativo da passare a dettaglio_evento.",
+ "type": "string"
+ },
+ "info_utili": {
+ "description": "Note pratiche: orari, come arrivare, prenotazioni.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "ingresso": {
+ "description": "Nullo quando l'atto non lo dichiara, ed e' il caso di gran lunga piu' frequente. Nullo NON vuol dire gratis: se manca, dillo, non dedurlo.",
+ "enum": [
+ "libero",
+ "pagamento",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "lat": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "locandina_url": {
+ "description": "La locandina, quando il comune ne ha pubblicata una.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "lon": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "luogo": {
+ "description": "Indirizzo o luogo preciso, quando l'atto lo dice.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "maps_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "organizzatore_ente": {
+ "description": "Chi organizza, quando e' un ente e non una persona.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "provincia": {
+ "description": "Sigla della provincia.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "regione": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "stato_temporale": {
+ "description": "Se e' in corso, in arrivo o concluso.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "titolo": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "updated_at": {
+ "description": "ISO 8601 UTC.",
+ "type": "string"
+ },
+ "url": {
+ "description": "La pagina dell'evento sul nostro sito: e' questo il link da citare.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "comune",
+ "url"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "evento"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail about what the response contains (description, practical info, organizer, free/paid status, official source link), which helps an agent know what to expect beyond the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single well-structured sentence conveys the purpose and the range of returned data without redundancy. The content enumeration is informative, and there is no filler or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple single-parameter read-only lookup with a rich output schema and complete annotations. The description names the main data categories, the schema documents the required id and its provenance, and the annotations cover idempotency and non-destructiveness. Nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the parameter description already explains that id is the event identifier returned by cerca_eventi. The description only paraphrases this ('a partire dal suo identificativo'), adding no new semantic meaning beyond the schema, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource ('un evento') and the scope ('tutti i dati'), including concrete content categories, but it lacks an explicit verb such as 'recupera' or 'restituisce'. It is clearly distinct from siblings by emphasizing full detail from an identifier, though it does not explicitly name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'a partire dal suo identificativo' plus the schema note 'come restituito da cerca_eventi' gives clear context: this tool should be used after search to fetch complete details for a known event ID. It does not spell out when to prefer cerca_eventi or comuni_coperti, but the ID provenance is an effective usage cue.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.