Skip to main content
Glama

One2Trip

Stato del viaggio

stato_viaggio
Read-only

Stato di un viaggio di componi_viaggio, subito: volo, tappe, auto, e a viaggio completo il totale a persona e booking_url. Solo lettura: nessuna ricerca, non consuma viaggi. Per aspettare il pezzo successivo usa attendi_viaggio.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "stato_viaggio"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesIl quote_id restituito da componi_viaggio.

Output Schema

NameRequiredDescriptionDefault
carNo
errorNo
stopsNo
flightNo
statusYessearching (chiama attendi_viaggio), complete, needs_review (una tappa da rivedere col cliente), error.
currencyNo
quote_idYes
next_stepYesCosa fare adesso.
travelersNo
link_untilNo
per_personNoSolo con complete: il totale del viaggio a persona, al centesimo, come sul sito (1224.5 = € 1.224,50). L'unico prezzo da dire: scrivilo come per_person_text.
price_noteNo
booking_urlNoSolo con complete: il link da mostrare così com'è.
retry_afterNo
review_reasonNoCon needs_review: airport_substitute = si aspetta il sì del cliente all'aeroporto sostituto (nessun totale né link).
per_person_textNoSolo con complete: per_person già scritto come sul sito (per esempio «€ 1.224,50»): da dire così com'è.
airport_substituteNo
taxes_at_property_per_personNoSolo con complete: tasse da pagare in hotel, a persona, non comprese.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered; the description nevertheless adds real behavior: the call returns immediately rather than blocking, it does not consume a trip, and it returns partial data that only gains the per-person total and booking_url once the trip is complete. The only gap is that it doesn't describe how to tell an incomplete trip apart structurally, which is partly served by the output schema.

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 dense sentences, front-loaded with the resource and the returned content before the read-only caveat and the sibling redirect. Slight redundancy in 'Solo lettura: nessuna ricerca' since read-only is already annotated, but the sentence is otherwise free of waste.

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?

An output schema exists, so return values need not be restated, and the description still conveys the progressive nature of the payload (complete vs. partial trip). For a one-parameter, non-destructive status read, everything an agent needs to call it and to interpret partial results is present.

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?

There is a single parameter with 100% schema description coverage stating it is the quote_id returned by componi_viaggio, so the schema carries the parameter burden. The description reinforces the provenance of the id but adds no format, validation, or error semantics beyond the schema, making the baseline 3 correct.

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?

Specific verb-and-resource: returns the state of a trip created by componi_viaggio, and enumerates what the state contains (volo, tappe, auto, totale a persona, booking_url). It also distinguishes itself from non-status operations with 'nessuna ricerca' and names the sibling attendi_viaggio, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to the alternative: 'Per aspettare il pezzo successivo usa attendi_viaggio' gives both the condition (waiting for the next piece) and the tool to use instead. It also states a when-not ('nessuna ricerca') and the immediacy of the call ('subito'), leaving little inference for the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources