Skip to main content
Glama

See Sight Tours

Search tours and trips

search_products
Read-onlyIdempotent

Use this when a traveler asks which See Sight Tours day tour, private tour or multi-day trip fits a city, starting point, date range, length or interest. Returns active products with stable ids, canonical seesight-tours.com links, from-prices and how each one books. Use location for where the tour happens and departure_city for where the traveler starts (e.g. Niagara Falls from Toronto). If notes say a place exists in two countries, ask the traveler which side.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoFree-text interests, e.g. 'boat ride', 'night tour', 'walking'.
localeNoSite language for links, e.g. 'en' (default) or 'es'.
countryNoCA or US. Niagara Falls: CA = Ontario side, US = New York side.
locationNoWhere the experience happens: city or region, e.g. 'Niagara Falls, Ontario'.
max_daysNo
min_daysNo
page_sizeNo
product_typeNo
departure_cityNoWhere the traveler starts, e.g. 'Toronto'.
max_duration_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that only ACTIVE products are returned, what fields accompany each result, and an ambiguity-handling rule for two-country places. It stops short of describing pagination limits or result ordering.

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?

Three sentences, each carrying distinct load: trigger condition first, return payload second, parameter disambiguation and edge-case handling last. No restatement of the name or title and no filler.

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 11 optional parameters, no output schema, and no required fields, the description correctly spends its budget on return contents and the location/departure_city distinction, which is what an agent most needs. It is not fully complete because result ordering, pagination behavior, and how the optional day/duration bounds combine are left unexplained.

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 only 45% across 11 parameters, so the description must compensate and it does so only for the most confusable pair: 'Use location for where the tour happens and departure_city for where the traveler starts (e.g. Niagara Falls from Toronto)' genuinely disambiguates two overlapping params. The remaining parameters (query, page, page_size, min_days, max_days, max_duration_hours, product_type, locale) get no added meaning, leaving the majority undocumented in prose.

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 gives a specific verb and resource ('search' for 'See Sight Tours day tour, private tour or multi-day trip') and enumerates the qualifying dimensions (city, starting point, date range, length, interest). It also states what comes back (active products with stable ids, canonical links, from-prices, booking method), so an agent can tell this apart from single-product siblings like get_product without opening any schema.

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 opening clause is an explicit trigger condition ('Use this when a traveler asks which ... fits a city, starting point, date range, length or interest'), which is strong when-to-use guidance. It falls short of a 5 because no when-not condition or named alternative sibling is given, so the agent must infer that get_product or check_availability handle narrower follow-ups.

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