Skip to main content
Glama

See Sight Tours

Check live availability and price

check_availability
Read-only

Use this when the traveler has picked a product and a date and wants open times and the exact total for their party. Reads live seats and prices; returns each departure's status, the total in minor units (cents) and a quote_id for create_checkout_session. Trips need one age per child in child_ages.

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>",
      "date": "<date>",
      "adults": "<adults>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct id from search_products, e.g. 'tour:<uuid>' or 'trip:<slug>'.
dateYesLocal date at the tour, YYYY-MM-DD.
adultsYes
localeNoSite language for links, e.g. 'en' (default) or 'es'.
infantsNo
childrenNo
currencyNo
child_agesNo

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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavioral context beyond that: data is read live (consistent with idempotentHint=false, as prices and seats change), and totals are returned in minor units (cents), which is a real gotcha for callers. It does not describe latency, sold-out/error behavior, or quote_id expiry, so a 3 fits.

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 compact sentences ordered as usage trigger, behavior/return shape, then a parameter caveat. No filler, and the routing-critical information (quote_id handoff, minor units) is front and center.

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?

There is no output schema, so the description carries the return-value burden and does so adequately: departure status, total in cents, and quote_id. With 8 parameters at 38% schema coverage, a couple of numeric parameters remain unexplained, but nothing required for a correct first call (id, date, adults, child_ages rule) is missing.

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 coverage is only 38% across 8 parameters, so the description must compensate. It does add a genuine business rule not present in the schema — trips need one age per child in child_ages — but leaves adults/children/infants counts, currency restriction (USD/CAD only), and the relationship between children and child_ages unexplained. Partial compensation for a notable coverage gap.

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 states a specific action and resource: reads live seats and prices for a chosen product and date, returning departure status and total. It is clearly distinguishable from siblings via the mention of quote_id for create_checkout_session and the implied step after search_products. It leans a little on the title's wording ('open times', 'exact total') rather than naming 'availability check' directly, which keeps it just short of 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?

The opening clause gives an explicit trigger condition — traveler has already picked a product and a date and wants open times and the exact total for their party — which also implicitly excludes the discovery stage handled by search_products. No explicit when-not-use or failure-mode guidance is given, and the downstream handoff to create_checkout_session is only implied through quote_id.

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