Skip to main content
Glama

One2Trip

Itinerari già pronti dei creator

find_ready_itinerary
Read-only

Gli itinerari già pronti, pubblicati dai creator, che corrispondono alla richiesta: tutti, senza tetto, dal più vicino alla richiesta e a parità in ordine casuale (non è una classifica). Solo lettura: non quota e non prenota; il cliente vede e prenota l'itinerario sul sito del creator. Chiamalo appena il cliente nomina un paese o una destinazione, prima di fare domande su date, persone o durata, e ogni volta che chiede un itinerario già pronto o cambia paese o luoghi. Argomenti: country (il paese), places (lat e lng dei luoghi nominati dal cliente: corrisponde un itinerario con una tappa entro radius_km da uno di essi), days solo se il cliente ha già detto la durata (corrisponde entro 2 giorni); serve almeno country o places. Ogni itinerario ha title, author_name (il creator), days e nights (N giorni / N-1 notti), price_from (il prezzo più basso della vetrina, a persona, in euro) e url da mostrare così com'è; se l'interfaccia mostra le card non ripeterli, altrimenti scrivi l'elenco con i link. Se itineraries è vuoto non dirne nulla e prosegui con il viaggio su misura. Mai confronti o classifiche fra creator; se il cliente sceglie l'itinerario di un creator, non proporgli alternative a quello.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_ready_itinerary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDurata in giorni (N giorni = N-1 notti), solo se il cliente l'ha già detta: corrisponde entro 2 giorni.
placesNoI luoghi che il cliente ha nominato (per esempio Kyoto): corrisponde un itinerario con una tappa vicina a uno di essi. Facoltativo.
countryNoIl paese di destinazione, in italiano o in inglese, per esempio Giappone.
radius_kmNoRaggio in km per places, da 1 a 500; facoltativo (predefinito 100).

Output Schema

NameRequiredDescriptionDefault
totalYesQuanti sono.
itinerariesYesTutti gli itinerari che corrispondono, dal più vicino alla richiesta (non è una classifica); vuoto se nessuno.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly/destructive/openWorld, but the description adds substantial behavior the agent cannot infer: no result cap, proximity ordering with random tie-breaking that is explicitly not a ranking, that quoting and booking happen on the creator's own site, output presentation rules (show url as-is, don't duplicate when cards are rendered), silent handling of empty results, and social constraints (never compare creators, never offer alternatives once one is chosen). This is unusually rich behavioral disclosure.

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?

Well front-loaded: purpose and scope first, then invocation timing, then parameters, then output/edge-case handling. The prose is dense and long-ish, but nearly every clause carries operational instruction. Minor redundancy exists between the parameter recaps and the schema, which already documents the same fields.

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 4-parameter read tool with annotations and an output schema, nothing an agent needs is missing: invocation timing, the hidden at-least-one-of requirement, result ordering, how to present fields, and what to do when the result set is empty. Return-shape explanation is legitimately limited because an output schema exists.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, and the description earns above that by supplying a cross-parameter rule the schema omits entirely: 'serve almeno country o places', despite the schema declaring zero required properties. It also clarifies conditional use of days (only if the client already stated a duration, matching within 2 days) and the proximity semantics of places. It largely restates the radius_km default rather than adding to it, which keeps it just below 5.

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?

Opens with a specific verb+resource: pre-built itineraries published by creators that match the request. It goes further than the name by stating scope ('tutti, senza tetto'), ordering ('dal più vicino alla richiesta e a parità in ordine casuale (non è una classifica)'), and explicitly separating itself from quoting/booking ('non quota e non prenota'). An agent can identify exactly which sibling (quote_trip / select_trip_option) this is not.

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?

Gives a precise trigger: call it as soon as the client names a country or destination, BEFORE asking about dates, people or duration. It also names re-trigger conditions ('ogni volta che chiede un itinerario già pronto o cambia paese o luoghi') and the fallback path when results are empty ('prosegui con il viaggio su misura'). Both when-to-call and what-not-to-do-first are explicit.

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