ViaggiaTreno MCP Server

Treni Su Tratta

treni_su_tratta

Retrieve currently running trains on a specific railway segment by supplying numeric IDs for both directions; get these IDs from the route list first.

Instructions

Restituisce i treni attualmente in circolazione su uno specifico segmento di tratta ferroviaria. Richiede gli identificativi numerici nei due sensi (tratta_ab e tratta_ba), ottenibili tramite elenco_tratte_ferroviarie.

Input Schema

TableJSON Schema

Name	Required	Default
`categorie`	No	ES*,IC,EXP,EC,EN,REG
`tratta_ab`	Yes
`tratta_ba`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose the key behavioral trait that results are limited to trains currently in circulation (a live snapshot rather than a schedule). It says nothing about freshness, pagination, permissions, or what happens with an invalid segment.

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 sentences, no filler, with the core behavior front-loaded and the prerequisite immediately after. Every sentence adds 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 details need not be repeated, and the prerequisite chain is covered. The remaining gap is the unmentioned category filter and any error behavior for invalid identifiers, which for a three-parameter read tool is a modest omission.

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 0%, and the description does explain the two required parameters as numeric directional identifiers plus where to source them, which is genuinely useful. However, the third parameter 'categorie' (train category filter with a default) is never mentioned, leaving a full third of the parameters undocumented.

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 states a specific verb and resource: it returns trains currently in circulation on a specific railway segment. It also distinguishes itself from the station-oriented siblings by scoping the query to a tratta segment identified by directional IDs.

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?

It explicitly states the prerequisite that the numeric identifiers for both directions must be obtained via elenco_tratte_ferroviarie, which is actionable routing information. It stops short of naming when not to use it or how it differs from real-time siblings like stato_treno.

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