experiences-oracle

Confronta il prezzo tra i provider

compare_experience

Read-only

Confronta il prezzo della STESSA esperienza tra i provider (Viator, Tiqets, Headout) e indica dove costa meno, con un verdetto e page_url, la pagina PIQOD dell'esperienza. USA QUESTO TOOL quando l'utente vuole il MIGLIOR PREZZO per un tour/attività specifico (passa l'experience_id ottenuto da search_experiences).

Nel risultato (lo stesso testo delle azioni GPT, api/oracle_openapi):
    min_people: Minimo di persone per prenotare, solo se il provider lo chiede ed è 2 o più: dillo accanto al
        prezzo («minimo 2 persone»). null = nessuno o ignoto. price_from non è il totale: a persona se
        price_basis=PER_PERSON, per unità se UNIT; con price_basis '' scrivi «minimo N persone» senza «a persona».
    price_basis: PER_PERSON | UNIT (prezzo per veicolo/gruppo/barca) | '' = dato non fornito dal provider (oggi
        disponibile sui prodotti Viator arricchiti; copertura in crescita).
    price_unit: VEHICLE/GROUP/BOAT/... quando price_basis=UNIT; altrimenti ''.
    page_url: Pagina PIQOD dell'esperienza (piqod.it), nella lingua del browser di chi la apre: lì ci sono descrizione, cosa è
        incluso, accessibilità (sedia a rotelle, sforzo fisico), lingue della guida, cancellazione, i giorni disponibili
        col prezzo del giorno e il tasto per prenotare. Questi dettagli NON sono nel risultato: se servono, apri la pagina.
        Dai SEMPRE questo link all'utente; non costruire mai link verso i provider.

Args:
    experience_id: id dell'esperienza (es. "viator_12345").
    query: (opzionale) la richiesta originale dell'utente.

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": {
      "experience_id": "<experience_id>"
    },
    "name": "compare_experience"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`experience_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 7, 2026

addedInput schema / properties / query

Added value: +{
+  "default": "",
+  "title": "Query",
+  "type": "string"
+}

Changed1 schema field changedJun 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "compare_experienceDictOutput",
+  "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?

Goes well beyond the readOnly/openWorld annotations: it warns that description, inclusions, accessibility, guide languages, cancellation and availability are NOT in the result and must be read on the linked page, and forbids constructing provider links. The result-field walkthrough (min_people, price_basis, price_unit) adds real behavioral context, though it partly duplicates the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and trigger are front-loaded, but the definition then expands into a long 'Nel risultato' block restating output fields and prescribing result phrasing ('dillo accanto al prezzo'). Since an output schema exists, this is largely redundant and inflates length with lowercase uppercase-emphasis formatting.

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?

Complete for the tool's complexity: what it compares, when to call it, the id provenance, the shape and caveats of the returned verdict, and the required user-facing link behavior are all covered.

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 0% schema description coverage, the description compensates: experience_id is explained with an example format ('viator_12345') and its provenance, and query is identified as optional and as the original user request. It does not explain whether/how query influences matching, so not a 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?

States a specific verb and resource — compare the price of the SAME experience across named providers (Viator, Tiqets, Headout) and return the cheapest with a verdict and PIQOD page_url. It is clearly distinguishable from search_experiences, which it names as the source of the experience_id.

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 trigger: 'USA QUESTO TOOL quando l'utente vuole il MIGLIOR PREZZO per un tour/attività specifico', plus the prerequisite that experience_id comes from search_experiences. That is enough for an agent to route correctly between this and the discovery tool.

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

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

Need Help?