Skip to main content
Glama
Sign In

In Viaggio alle Canarie

by it.inviaggioallecanarie
OverviewDiscussionsAdmin

cerca_offerte

Cerca offerte pacchetto volo+hotel+auto/transfer per le Isole Canarie. Tutte le offerte sono attive, con prezzo "da" a persona su base 2 persone. IMPORTANTE: per condividere un'offerta usa SEMPRE ed ESATTAMENTE il valore del campo "link" di quel risultato, copiandolo carattere per carattere. Non costruire, abbreviare, indovinare o comporre URL a partire da isola, zona o altri campi: gli URL contengono un identificativo che non è deducibile e un link inventato porta il cliente su una pagina di offerta inesistente. Se non hai il campo "link" di un'offerta, richiama questo strumento invece di dedurlo. Per le crociere (MSC, crociera di gruppo con Toda Canarias) usa il tool crociere, non questo.

Input Schema

NameRequiredDescriptionDefault
meseNoMese di partenza in formato YYYY-MM (es. 2026-09)
zonaNoZona/località (es. Costa Adeje, Maspalomas, Corralejo)
isolaNoIsola di destinazione
fasciaNoFinestra di partenza: last_minute 0-60gg, medio_termine 60-120gg, lungo_termine 120-180gg
limiteNoRisultati massimi (default 10, max 20)
ordinaNoOrdinamento (default: prezzo crescente)
num_nottiNoDurata esatta in notti
board_typeNoTrattamento: AI=All Inclusive, HB=Mezza Pensione, BB=B&B
budget_maxNoBudget massimo a persona in EUR
stelle_minNoStelle hotel minime (3-5)
aeroporto_partenzaNoCodice IATA dello scalo italiano di partenza (non il nome della città)
solo_con_escursioniNoSolo offerte con escursioni incluse

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / aeroporto_partenza / description
      Previous value: -"Codice IATA italiano: MXP, LIN, BGY, TRN, VRN, TSF, BLQ, PSA, FCO, NAP"New value: +"Codice IATA dello scalo italiano di partenza (non il nome della città)"
    • addedInput schema / properties / aeroporto_partenza / enum
      Added value: +[
+  "BGY",
+  "BLQ",
+  "FCO",
+  "LIN",
+  "MXP",
+  "NAP",
+  "PSA",
+  "TRN",
+  "TSF",
+  "VRN"
+]
  2. First observed

TDQS

A4.4/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 behavioral burden: it discloses that all offers are active, that pricing is 'da' per person based on 2 people, and that 'link' values must be copied exactly because invented URLs lead to nonexistent offers. It could add more about result shape or pagination, but the critical caveats are present.

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?

The description is compact and structured: purpose first, then pricing and behavioral warnings, then the sibling-tool exclusion. Every sentence carries necessary routing or safety information, with no filler.

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?

Given 12 fully documented parameters, no output schema, and no annotations, the description adequately covers destination, package type, pricing basis, link-handling rules, and the cruises exclusion. It does not describe the full result contract, but the absence of an output schema makes that a moderate rather than critical gap.

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 every parameter has a description with examples or enums, so the baseline is 3. The description adds context about the 'link' result field but does not add new parameter-level semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'offerte pacchetto volo+hotel+auto/transfer per le Isole Canarie.' It also distinguishes itself by stating that cruises belong to the sibling tool crociere, making the scope clear.

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?

It gives an explicit exclusion: 'Per le crociere (MSC, crociera di gruppo con Toda Canarias) usa il tool crociere, non questo.' It also instructs the agent to call this tool again when no 'link' field is available, rather than constructing a URL, which is direct when-to-use guidance.

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

All In Viaggio alle Canarie toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources