Skip to main content
Glama

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.

Input Schema

TableJSON 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/5.0
Behavior4/5

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

With no annotations, the description carries the burden and reveals key behaviors: all offers are active, pricing is 'from' per person based on 2 people, and the link field contains a non-deducible identifier that must be copied exactly. This prevents a common failure mode where an agent invents a URL. It doesn't cover all possible behaviors, but it's meaningful.

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 three sentences, with the purpose first and the critical link-handling instruction immediately after. Every sentence earns its place; the warning is detailed but necessary to prevent hallucinations.

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?

For a tool with 12 parameters and no output schema, the description explains the pricing basis and the crucial link field behavior. It doesn't elaborate on the full output structure, but the schema covers input parameters and the link warning is the most important runtime caveat.

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?

The schema already provides 100% description coverage for all 12 parameters, including enums and examples. The tool description adds no extra parameter semantics, so a baseline of 3 is appropriate.

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 clearly identifies the tool as searching for flight+hotel+car/transfer package offers in the Canary Islands, with a specific verb and resource. It doesn't explicitly mention sibling tools like cerca_hotel, but the phrase 'pacchetto volo+hotel+auto/transfer' makes it distinct.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (when searching package offers) and includes a critical instruction on how to handle the 'link' field in results. However, it doesn't explicitly state when not to use this tool in favor of a sibling, so it falls short of a 5.

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