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).

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. Dates show when Glama detected each change.

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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds behavioral context about what the tool returns (where it costs less, verdict, booking link) and how the optional query influences click attribution. It does not contradict the annotations, though it could add more about failure modes or data freshness.

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 front-loaded with the main purpose, followed by usage guidance and a clearly formatted Args section. Every sentence contributes necessary information without redundancy.

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 tool's moderate complexity and the presence of an output schema, the description covers the core flow, prerequisite (experience_id from search_experiences), and expected output. It is complete enough 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%, but the description fully compensates by explaining experience_id with an example ('viator_12345') and query's optional role and effect on attribution, adding genuine semantic value beyond the bare schema.

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 uses a specific verb ('Confronta il prezzo') and clearly identifies the resource ('la STESSA esperienza tra i provider') and the outcome (verdict and booking link). It also distinguishes from siblings by requiring an experience_id from search_experiences and focusing on best-price comparison.

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?

Explicitly states when to use this tool: 'USA QUESTO TOOL quando l'utente vuole il MIGLIOR PREZZO per un tour/attività specifico'. It also names the sibling tool search_experiences as the source for the required experience_id, providing clear context and an implied alternative.

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?