Skip to main content
Glama

hoteldiscount24 Hotels

Find a destination

find_place
Read-onlyIdempotent

Use when a city, region or island name has to be turned into a place_id (needed by search_hotels, get_hotel_facts and get_price_guide): returns up to 5 matching places with place_id and country. A misspelled name returns the likely places; the match field says whether a place is exact, partial or fuzzy. If several fit, choose by country or ask the user.

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": {
      "query": "<query>"
    },
    "name": "find_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCity, region or island name, in any language.
languageNoThe user's language: de, en or tr (default en).

Output Schema

NameRequiredDescriptionDefault
noteNo
placesYes
sourceNo
websiteNo
response_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / places / items / properties / match
      Added value: +{
      +  "enum": [
      +    "exact",
      +    "partial",
      +    "fuzzy"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description then adds genuinely new behavior: capped at 5 results, misspellings return likely candidates, and the result carries a match field graded exact/partial/fuzzy. That is beyond anything the annotations or schema convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The trigger leads, the consumers and the return shape follow, and the multi-match fallback closes. Every clause carries information; there is no filler.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the key return fields and the match-quality signal, and it explains the tool's role in the larger hotel-lookup flow. Nothing an agent needs to invoke it correctly is absent.

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% — both 'query' (city/region/island, any language, 2-80 chars) and the 'language' enum are already documented. The description restates the resource type but adds no syntax, formatting or defaulting detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise transformation — a city/region/island name becomes a place_id — and immediately names the sibling tools that consume it (search_hotels, get_hotel_facts, get_price_guide). An agent can distinguish it from those siblings without opening any schema.

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

Usage Guidelines5/5

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

Opens with an explicit trigger condition ('Use when a city, region or island name has to be turned into a place_id') and closes with disambiguation advice when multiple places match. This is the when-to-use plus alternatives pattern done well.

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