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 il link di prenotazione. 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 ''.

Args:
    experience_id: id dell'esperienza (es. "viator_12345").
    query: (opzionale) la richiesta originale dell'utente — migliora
        l'attribuzione del click; se assente si usa il titolo.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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.4/5.0

Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already declared, the description adds useful behavioral context: it compares across specific providers, returns a verdict and booking link, and explains how to interpret min_people, price_basis, and price_unit. It does not contradict the annotations, though it does not cover rate limits or provider availability limits.

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?

The purpose and usage guidance are front-loaded, but the description is long and spends substantial space explaining result fields despite the tool having an output schema. It also includes an internal reference ('lo stesso testo delle azioni GPT, api/oracle_openapi') that does not help an external agent select or invoke the tool.

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 two-parameter read-only comparison tool with annotations covering safety and an existing output schema, the description supplies the missing pieces: exact purpose, when to use it, prerequisite data source, and parameter meanings. Nothing essential for correct invocation appears to be missing.

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 carries the parameter burden and does so well. It defines experience_id with an example format and explains that query is optional, improves click attribution, and defaults to the experience title if absent.

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 names a specific verb and resource: compare the price of the SAME experience across providers and indicate the cheapest option. It also distinguishes the tool from siblings by making clear that search_experiences is the source of experience_id and that this tool specifically provides the best-price verdict.

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?

It gives explicit when-to-use guidance: 'USA QUESTO TOOL quando l'utente vuole il MIGLIOR PREZZO per un tour/attività specifico'. It also states the prerequisite of passing an experience_id obtained from search_experiences. However, it does not state when not to use the tool or name an alternative comparison path.

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?