Skip to main content
Glama

Nusa Penida Holiday Planner

Hotels auf Nusa Penida suchen

search_hotels
Read-onlyIdempotent

Sucht Hotels mit Filtern (Ort, Preisrange, Rating-Range) und Pagination. Liefert Booking-Deeplink und Detail-URL.

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_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTrefferzahl (1-50, default 20).
queryNoFreitext-Suche im Hotelnamen.
offsetNoOffset für Pagination (0-500, default 0).
sort_byNoSortierung, default rating_desc.
locationNoOrtsfilter, z.B. 'Toyapakeh', 'Ped', 'Sampalan'.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the response payload (Booking-Deeplink und Detail-URL) and the pagination behavior, which matters because there is no output schema. It stops short of stating defaults or result ordering semantics, hence a 4 rather than 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with zero filler; the filter capability is front-loaded before the return-value note. It is efficient, though the second sentence could be folded in or expanded slightly for structure.

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 nine-parameter read-only search with a fully documented schema and no output schema, the description covers the essentials: what is searched, what can be filtered, and what comes back (deeplink plus detail URL). Only the absence of guidance on combining filters or choosing between this and sibling discovery tools leaves a minor gap.

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% across all nine parameters, so limit, offset, sort_by, query and the price/rating bounds are fully documented in the schema. The description only echoes three filter families (Ort, Preis, Rating) and adds no syntax, units, or default information beyond structured data, 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?

"Sucht Hotels mit Filtern" states a concrete verb plus resource, and the parenthetical enumerates the filter dimensions (Ort, Preisrange, Rating-Range) plus Pagination. It is instantly distinguishable from the list_* and search_tours siblings, but it never names an alternative explicitly, so it stops short of full sibling differentiation.

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?

The description says what can be filtered but gives no when-to-use condition, no prerequisites, and no exclusions (e.g. when to prefer get_best_price or list_activities). The agent must infer from the tool name alone when this search is the right call.

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