Skip to main content
Glama

Amsterdam Experiences

Send a booking inquiry

submit_inquiry

Submit a tour booking inquiry. Returns confirmation when the inquiry is received. A member of the Amsterdam Experiences team replies by email to confirm availability.

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_slug": "<tour_slug>",
      "date": "<date>",
      "guests": "<guests>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesPreferred tour date in YYYY-MM-DD format
nameYesFull name of the person making the inquiry
emailYesEmail address for booking correspondence
guestsYesNumber of guests (adults) in the group
messageNoOptional message or special requests
tour_slugYesTour slug identifying the requested tour

Output Schema

NameRequiredDescriptionDefault
inquiryYesResponse from the inquiry API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds real context beyond that: the inquiry is not a confirmed booking, a human team member responds by email, and the result is a receipt confirmation. It leaves unstated whether data is retained or how duplicate submissions are handled, but with annotations covering the safety profile this is solid additional value.

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?

Three short sentences, front-loaded with the action and followed by outcome and workflow. The sentence 'Returns confirmation when the inquiry is received' is mildly redundant given an output schema exists, which is the only real waste.

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 non-idempotent, open-world submission tool the description conveys the key mental model: this is an inquiry, not a reservation, and resolution happens asynchronously by email. An output schema covers return values, so the remaining gap is only the absence of guidance on required sequencing or duplicate submissions.

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%, with all six parameters documented including format hints (YYYY-MM-DD) and the optional message field. The description adds no parameter-level meaning, so the baseline 3 applies since the schema does the heavy lifting.

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: 'Submit a tour booking inquiry', which is clearly distinguishable from the sibling read tools get_tour_details and search_tours. It does not explicitly name those siblings or contrast with them, keeping 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 Guidelines3/5

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

The description implies usage through the follow-up workflow ('A member of the Amsterdam Experiences team replies by email'), so an agent can infer this is the step after browsing tours. However, there is no explicit when-to-use versus when-not guidance, no statement that get_tour_details should be consulted first for the tour_slug, and no note about what to do if a booking is already confirmed.

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