Skip to main content
Glama

One2Trip

Attendi il viaggio

attendi_viaggio
Read-only

Come stato_viaggio, ma se il viaggio si sta ancora componendo aspetta sul server fino a circa 20 secondi il pezzo successivo (volo, una tappa, l'auto o la chiusura). Solo lettura. Chiamalo dopo componi_viaggio finché status è searching: di solito bastano 2 o 3 chiamate.

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": "attendi_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.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so 'Solo lettura' is largely redundant but consistent. The description adds genuinely useful behavior the annotations cannot convey: a server-side wait of roughly 20 seconds and what event unblocks it. It stops short of 5 because it doesn't say what is returned if the wait expires with nothing new.

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?

Three tight sentences, front-loaded with the sibling comparison so the reader immediately knows the baseline behavior, then the delta, then the call pattern. Little waste; the opening reference does compress a lot of meaning into a few words, at the cost of some self-containedness.

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 values needn't be explained, and with one fully documented parameter the remaining burden is behavioral — which the long-poll timing and loop guidance largely cover. The only meaningful gap is the post-timeout outcome, which matters for an agent deciding whether to retry.

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 coverage is 100% and the single quote_id parameter is already documented in the schema as coming from componi_viaggio. The description reinforces that workflow link but adds no syntax or meaning beyond the schema, so the baseline 3 applies.

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?

The description defines the tool as a variant of stato_viaggio with a specific delta: if the trip is still composing, it blocks server-side for up to ~20 seconds awaiting the next piece (flight, leg, car, or closure). That is a concrete verb+resource+behavior. It falls short of a 5 because the core semantics are pinned to a sibling reference ('Come stato_viaggio, ma...'), so an agent must already know what stato_viaggio does to fully resolve the purpose.

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?

Explicit when-to-use: call it after componi_viaggio while status is 'searching', and it even sets an expectation that 2-3 calls usually suffice. The alternative (stato_viaggio) is invoked by the opening comparison, giving the agent a clear routing choice between polling and long-polling.

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