Skip to main content
Glama

Nusa Penida Holiday Planner

Touren & Ausflüge suchen

search_tours
Read-onlyIdempotent

Sucht buchbare Touren mit Filtern (Preisrange, Rating-Range) und Pagination.

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
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
providerNoAnbieter, z.B. 'GetYourGuide', 'Viator', 'Klook'.
max_priceNoHöchstpreis in EUR.
min_priceNoMindestpreis in EUR.
max_ratingNoHöchst-Rating (0-10).
min_ratingNoMindest-Rating (0-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower. The description adds that results are limited to bookable tours and that filtering plus pagination are supported, but it says nothing about result volume, ranking defaults, or what the openWorldHint=false boundary means for coverage.

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?

A single front-loaded sentence with no filler. It is efficient, though the terse phrasing leaves room for one more clause about search input or provider filtering without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, zero-required search tool with no output schema, the definition covers the headline capability but omits several parameters and any hint about default behavior or result shape. It is adequate but leaves the agent to read the schema for the bulk of the semantics.

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 coverage is ~78%, so the schema already documents most parameters including price/rating bounds and pagination limits. The description only echoes the price and rating range concepts and does not mention the free-text query, provider filter, or sort_by enum, so it adds little beyond the schema.

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 ('Sucht buchbare Touren') plus the capability set (filters, pagination), so an agent immediately knows this is a tour search rather than a list or a booking action. It never names a sibling such as list_activities, so differentiation from the other tour/activity tools is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the sibling list_* or search_* tools, and no exclusions or prerequisites. The only contextual cue is the word 'buchbare', which implies it returns bookable products but is not framed as guidance.

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