Skip to main content
Glama

Discover Canal Cruises – private tours in Leiden

Get price

get_price
Read-onlyIdempotent

Exact price for a group on a date (prices can depend on the season), including chosen extras and the VAT breakdown. Same calculation as the booking page.

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>",
      "date": "<date>",
      "guests": "<guests>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTour date, YYYY-MM-DD.
tourYesTour id (the "tour" value from list_tours, e.g. "cosy-tour").
guestsYesNumber of guests in the group (adults and children together).
optionsNoOptional extras, keyed by option id (or option name) from get_tour. Value: the chosen text for a choice, true for a yes/no extra, a number for a quantity.

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 genuinely useful behavior beyond that: the result is season-dependent, includes selected extras, and contains a VAT breakdown. It still says nothing about error behavior for invalid option ids or whether prices can vary between calls.

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 short sentences, front-loaded with the core purpose, then the differentiating detail ('same calculation as the booking page'). No filler or restatement of the tool name.

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?

No output schema exists, and the description adequately covers the return shape (price plus VAT breakdown, extras included). The main omission is currency and whether the response includes a per-guest breakdown, which would matter for a pricing tool with a nested options object.

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%, including a detailed nested options description, so the schema carries parameter meaning. The description only echoes the ideas ('chosen extras', group on a date) without adding format or constraint detail beyond it. Baseline 3 is appropriate here.

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 operation (return the exact price) over a specific resource (a group on a date), and adds scope qualifiers: seasonal dependence, chosen extras, VAT breakdown. 'Same calculation as the booking page' distinguishes it from an indicative/from-price listing. It does not explicitly name a sibling it supersedes, but the resource is unambiguous.

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?

Usage is implied rather than stated: an agent can infer this is the tool for a final, bookable price rather than availability (check_availability) or tour details (get_tour). There is no explicit when-to-use, when-not, or prerequisite (e.g. 'call get_tour first to obtain option ids') guidance in the description itself.

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