ViaggiaTreno MCP Server

Tabellone Arrivi

tabellone_arrivi

Retrieve real-time arrival boards for a chosen Italian railway station, including scheduled and actual times, delays, platforms, and whether each train has arrived.

Instructions

Restituisce il tabellone degli arrivi in tempo reale per una stazione ferroviaria (es. 'S01700' per Milano Centrale). Fornisce: treni in arrivo, stazione di provenienza, orario programmato, ritardo in minuti, binario programmato ed effettivo, e se il treno è già giunto in stazione.

Input Schema

Name	Required	Description	Default
`data_ora`	No
`codice_stazione`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 24, 2026

changedOutput schema / properties / result / items / properties / compRitardo / anyOf

Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / result / items / properties / compRitardo / description

Previous value: -"Testo del ritardo multilingua"New value: +"Testo del ritardo multilingua (elementi possono essere null, osservato dal vivo)"

First observedv0.1.0Oct 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose 'in tempo reale' (live data) and enumerates the returned fields, which implies a read-only operation, but it never states auth/permission needs, rate limits, or how data_ora changes the result set.

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 core purpose, no filler. The field enumeration is long-ish but earns its place given the schema documents nothing; only slight redundancy against the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the returned-field list is largely duplicated, and the exclusion of any guidance on data_ora leaves a real gap for a 2-parameter tool. Adequate for the common case of a current-arrivals lookup but incomplete around the optional time parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. The description compensates for codice_stazione by giving an example value format ('S01700'), but data_ora is not mentioned at all, leaving an entire parameter — presumably a timestamp for querying a non-current timetable — unexplained in either schema or description.

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 and resource ('Restituisce il tabellone degli arrivi in tempo reale per una stazione ferroviaria') and gives a concrete station-code example ('S01700' per Milano Centrale). The arrivals scope cleanly separates it from the obvious counterpart, tabellone_partenze.

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?

Usage is only implied: an agent can infer this is for looking up live arrivals at a given station. There is no explicit when-to-use/when-not, no mention of tabellone_partenze or stato_treno as alternatives, and no stated prerequisites.

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