Skip to main content
Glama

Discover Canal Cruises – private tours in Leiden

Check availability

check_availability
Read-onlyIdempotent

Free start times of a tour per day. Tours can be booked far ahead (usually up to a year; the result says until when in bookable_until). Each call covers at most 31 days from date_from (default 14); date_from can be any date up to bookable_until, so call again for later periods. Times are local Leiden time. When nothing is free in the range, next_available_date tells the first day with a free time.

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": {
      "tour": "<tour>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
tourYesTour id (the "tour" value from list_tours, e.g. "cosy-tour").
guestsNoNumber of guests in the group (adults and children together).
date_toNoLast day, YYYY-MM-DD (inclusive).
date_fromNoFirst day, YYYY-MM-DD, any date up to bookable_until. Default: today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds substantial context: a hard 31-day window per call, the bookable_until horizon, the Leiden timezone, and the next_available_date fallback when nothing is free. These are exactly the edge cases an agent would otherwise discover only by trial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, purpose front-loaded, with no filler. The opening is a noun phrase rather than a verb phrase, and the '(default 14)' shorthand is compressed to the point of ambiguity, but overall it is tightly written.

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 return-value burden and does disclose key fields (bookable_until, next_available_date) plus timezone and range limits. It does not describe the shape of the returned free-time list per day, which is the one remaining gap for an agent parsing results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: date_from can be any date up to bookable_until, the effective range is capped at 31 days, and the default span is 14. The parenthetical '(default 14)' sits slightly at odds with the schema's 'Default: today' for date_from, a small ambiguity that keeps it from a 5.

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 opening sentence 'Free start times of a tour per day' names a specific resource (tour availability) and output (free start times), which an agent can easily separate from get_price or get_tour. It does not explicitly name a sibling tool it replaces or differs from, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives procedural guidance for the 31-day window ('call again for later periods') and states the default span, which is genuinely useful. However, it never says when to prefer this over get_price or create_booking_link, nor any precondition such as needing a tour id from list_tours (that hint lives only in the schema).

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