Skip to main content
Glama

See Sight Tours

Get tour or trip details

get_product
Read-onlyIdempotent

Use this when the traveler wants the facts about one See Sight Tours product: what is included and excluded, itinerary, meeting point or pickup, cancellation terms, price options and the right page to book or request it. Only states facts published on seesight-tours.com.

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": {
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct id from search_products, e.g. 'tour:<uuid>' or 'trip:<slug>'.
localeNoSite language for links, e.g. 'en' (default) or 'es'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and repeatability are covered structurally. The description adds one genuinely useful behavioral constraint: 'Only states facts published on seesight-tours.com', telling the agent the output is grounded in a single source and will not synthesize beyond it. Missing are behaviors the annotations do not cover, such as what happens with an unknown or stale product id.

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?

Two sentences with no filler: the trigger condition is front-loaded, the returned content is enumerated in a compact list, and the source-grounding caveat follows. Every clause carries information the agent can act on.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating inclusions, itinerary, meeting point, cancellation terms, prices, and a booking link. For a two-parameter read-only tool this is nearly complete; only edge-case behavior for invalid ids is left unstated.

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?

Schema description coverage is 100%, with both the id format ('tour:<uuid>' or 'trip:<slug>') and the locale enum documented in the schema itself. The description contributes 'one ... product', reinforcing that id must identify a single item, but adds no extra syntax or format guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb-and-resource pair implicitly ('the facts about one See Sight Tours product') and enumerates the exact contents returned: inclusions/exclusions, itinerary, meeting point, cancellation terms, price options, and booking page. This is far more specific than a restated title and effectively scopes it to a single product, distinguishing it from a search tool. It stops short of naming the sibling it differs from (search_products), which keeps it from a 5.

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?

'Use this when the traveler wants the facts about one See Sight Tours product' gives a clear triggering condition tied to a single-item lookup rather than a broad search. There is no explicit when-not clause and no sibling alternative is named, so the agent must infer that discovery belongs to search_products. Clear context without exclusions fits a 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources