experiences-oracle

Cerca esperienze, tour e biglietti

search_experiences

Read-only

Cerca tour, attività ed esperienze da prenotare in un luogo o per un intento di viaggio (es. "cosa fare a Roma", "biglietti per il Colosseo", "tour in barca a Capri"). Restituisce risultati reali con città, prezzo, rating e un link di prenotazione (redirect PIQOD affiliato). USA QUESTO TOOL quando l'utente cerca cose da fare, tour, attività, biglietti o esperienze in una destinazione. IMPORTANTE per la coerenza: se l'utente nomina un'ATTRAZIONE/attività precisa (es. "tour del Colosseo"), passa quel nome in keyword (es. "Colosseo") → i risultati saranno SUL Colosseo, non genericamente vicini. Mappa anche gli INTENTI sui filtri: "salta fila/skip the line" → skip_the_line=True; "più economico/cheapest" → sort="price"; "cancellazione gratuita" → free_cancellation=True.

Args:
    query: intento o luogo dell'utente.
    location: luogo esplicito (override di query), opzionale.
    category: categoria/filtro tematico, opzionale.
    budget_max: prezzo massimo, opzionale.
    keyword: attrazione/attività specifica da matchare nei titoli (es. "Colosseo").
    skip_the_line: True se l'utente vuole biglietti/tour "salta fila".
    free_cancellation: True se vuole cancellazione gratuita.
    sort: "price" per i più economici prima (default "rating").
    limit: numero risultati (max 50).

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	rating
`limit`	No
`query`	Yes
`keyword`	No
`category`	No
`location`	No
`budget_max`	No
`skip_the_line`	No
`free_cancellation`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "search_experiencesDictOutput",
+  "type": "object"
+}

First observedJun 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and destructiveHint, so the burden is lower. The description adds useful behavioral context: it returns real results, redirects to a PIQOD affiliate link, and explains parameter behavior. No contradictions with annotations.

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?

The description is moderately long but well-structured with a clear flow: what it does, when to use, important notes, parameter mapping. It could be slightly more concise, but every sentence adds value. The bilingual Italian-English may cause minor readability issues.

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?

Given the complexity (9 parameters, 1 required) and the presence of an output schema, the description covers all necessary aspects: purpose, usage with examples, parameter semantics, and behavioral traits (affiliate redirect). It is complete for an agent to select and invoke correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does so thoroughly, explaining each parameter's meaning and how to map user intents (e.g., keyword for specific attractions, skip_the_line for skip-the-line requests). This far exceeds the baseline needed for 9 parameters.

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 clearly states the tool searches for tours, activities, and experiences to book in a location or travel intent. It uses specific verbs ('Cerca') and resources ('tour, attività ed esperienze'), and distinguishes itself from siblings by mentioning it returns real results with city, price, rating, and an affiliate link.

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 explicitly says 'USA QUESTO TOOL quando l'utente cerca cose da fare...' and provides detailed guidance on mapping user intents to parameters (e.g., 'skip-the-line' -> skip_the_line=True). However, it does not explicitly state when not to use it or offer alternatives to siblings.

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

All experiences-oracle tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?