Skip to main content
Glama

Profilo Treno

profilo_treno

Analisi di un treno da andamentoTreno: stato (regolare, soppresso, parziale), avanzamento, itinerario programmato, fermate nell'ordine di marcia con orari e binari programmati/effettivi, archi tra fermate consecutive (tempi di percorrenza…

Instructions

Analisi di un treno da andamentoTreno: stato (regolare, soppresso, parziale), avanzamento, itinerario programmato, fermate nell'ordine di marcia con orari e binari programmati/effettivi, archi tra fermate consecutive (tempi di percorrenza, ritardo accumulato, soste), collegamento programmato ed effettivo e anomalie. Se codice_stazione_origine e data_partenza mancano si ricavano dal numero di treno. Restituisce null se l'API non ha il treno (prima della partenza o dopo il reset notturno).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "numero_treno": "<numero_treno>"
    },
    "name": "profilo_treno"
  }
}

Input Schema

NameRequiredDescriptionDefault
numero_trenoYes
data_partenzaNo
codice_stazione_origineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: the two optional parameters can be inferred from the train number, and the call returns null when the API has no train (before departure or after the nightly reset). It still omits auth/permission expectations and whether these are live snapshots, but the null-contract and fallback behavior are exactly what an agent needs.

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?

The purpose comes first, followed by two short sentences on fallback derivation and the null return, so it is front-loaded and has no filler. The opening enumeration is dense and long, but each item corresponds to a real content category rather than padding.

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?

For a three-parameter read tool with an output schema, the description covers the open questions: parameter derivation, null semantics, and the shape of the returned analysis. The return enumeration is somewhat redundant with the output schema, but nothing an agent needs to invoke 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 description coverage is 0%, so the description must compensate: it explains the derivation of codice_stazione_origine and data_partenza, which is genuine added meaning. The format of data_partenza (an integer date, presumably YYYYMMDD) and of codice_stazione_origine remain undocumented anywhere.

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?

It names a specific verb/resource (analysis of a train from andamentoTreno) and enumerates exactly what the profile contains: state, progress, itinerary, stops, arcs, connection and anomalies. It does not, however, distinguish itself from close siblings such as stato_treno or profilo_stazione, so an agent must infer the boundary.

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 implied by the required numero_treno and the note that origin station and departure date can be derived, which tells the agent it can call with just a train number. There is no explicit when-to-use/when-not or routing to alternatives like stato_treno for a lighter status check.

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