Skip to main content
Glama

Discover Canal Cruises – private tours in Leiden

Tour details

get_tour
Read-onlyIdempotent

Full details of one tour: description, departure point, duration, group size, prices (incl. seasonal prices), regular start times, optional extras with their ids and prices, cancellation policy and contact details.

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": "get_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
tourYesTour id (the "tour" value from list_tours, e.g. "cosy-tour").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 the safety profile is covered. The description adds value by disclosing the concrete contents of the response (seasonal prices, extras with ids, cancellation policy, contact details), which is behavioral context beyond the annotations. It does not say what happens for an unknown tour id, so it is not a 5.

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?

A single front-loaded sentence with a colon-delimited field list; every item earns its place because there is no output schema to convey return contents. No redundant wording or preamble.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the description is close to complete: it carries the return-value burden thoroughly. Minor gaps remain around error behavior for an invalid id and whether seasonal prices require any date context.

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?

With a single parameter at 100% schema description coverage, the schema already explains the tour id, gives an example format ('cosy-tour'), and points at list_tours as the source. The description adds nothing further about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Full details of one tour') and enumerates the exact payload fields returned, so an agent knows precisely what it gets. It does not explicitly contrast with siblings such as get_price or list_tours, 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?

There is no explicit when-to-use or when-not-to-use guidance; the usage is only implied (fetch the full record for a single tour id, presumably after list_tours). No alternative is named, so the agent must infer routing from sibling names alone.

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