Skip to main content
Glama

Nusa Penida Holiday Planner

Günstigsten Preis über alle Partner finden

get_best_price
Read-onlyIdempotent

Liefert für ein Hotel, eine Tour oder eine Fähre den günstigsten bekannten Preis über alle Partnerplattformen (Booking, Agoda, GetYourGuide, Viator, Klook) inklusive Quell-URL.

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": {
      "category": "<category>"
    },
    "name": "get_best_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoExakter Slug, z.B. 'kelingking-secret-view'.
queryNoAlternativ: Namenssuche, wenn der Slug unbekannt ist.
categoryYesKategorie des Angebots.

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 readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine behavioral value beyond that by naming the aggregated sources (Booking, Agoda, GetYourGuide, Viator, Klook) and stating the response includes a source URL, but says nothing about missing prices, staleness, or aggregation rules.

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; the partner list is parenthetical and optional but does add information. Nothing needs trimming.

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 simple read-only lookup with a fully described three-parameter schema and no output schema, the description covers what the tool returns (cheapest price plus source URL). It is silent on failure/empty-result behavior and on the slug-vs-query selection strategy, which leaves real gaps for an agent.

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%, so slug, query and category are already documented, including the slug/query fallback relationship. The description only echoes the category choices as prose ('Hotel, Tour oder Fähre'), which adds little beyond the enum.

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 ('Liefert') and a precise resource ('günstigsten bekannten Preis über alle Partnerplattformen') and even enumerates the partner platforms. It does not explicitly distinguish itself from siblings such as search_hotels or search_tours, which is what keeps it from 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 Guidelines2/5

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

There is no guidance on when to call this versus the list/search siblings, and no hint about when to prefer slug over query. The agent must infer that this is a follow-up price-comparison step after discovery.

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