Skip to main content
Glama

Amsterdam Experiences

Search tours

search_tours
Read-only

Search for available private guided tours in Amsterdam and the Netherlands. Returns tour names, prices, slugs and descriptions, shown as tour cards where the client supports it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tours"
  }
}

Input Schema

NameRequiredDescriptionDefault
tour_typeNoFilter by tour type: 'private' (whole group pricing) or 'small_group' (per person pricing)

Output Schema

NameRequiredDescriptionDefault
toursYesMatching tours

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds return fields and client-dependent tour-card display behavior, but it does not discuss pagination, result limits, or other operational details.

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?

The description is two sentences and front-loads the core search purpose. The second sentence is useful for display behavior but partly redundant with the existing output schema.

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 low-complexity search tool with one optional parameter, annotations, and an output schema, the description is largely complete. It could be stronger with explicit guidance on the tour_type filter and sibling alternatives.

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%, and the single tour_type enum is fully documented in the schema. The description does not add parameter meaning beyond the schema, and its emphasis on 'private guided tours' does not fully reflect the available small_group option.

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 verb and resource: searching available private guided tours in Amsterdam and the Netherlands. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as get_tour_details.

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 by 'Search for available private guided tours,' but there is no explicit when-to-use guidance, no exclusions, and no mention of when to use get_tour_details instead.

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