Skip to main content
Glama

hoteldiscount24 Hotels

Checked travel knowledge for a destination

get_travel_knowledge
Read-onlyIdempotent

Use when the user asks about the destination itself rather than a hotel, e.g. the best time to travel or the climate per season: hoteldiscount24's checked travel knowledge for the place, the same text Mercan uses in its chat. has_knowledge=false means there is no checked text for this place and topic — say so, do not guess.

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": {
      "place_id": "<place_id>",
      "topic": "<topic>"
    },
    "name": "get_travel_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic: anreise = Getting there & around; ausfluege = Day trips & activities; einkaufen = Shopping & markets; essen = Food & drink; feste = Festivals & events; gut_zu_wissen = Good to know; kunst_kultur = Art & culture; nachtleben = Nightlife & going out; reisezeit = Best time to travel & climate; stadtteile = Neighbourhoods & where to stay; strand = Beaches & swimming; wintersport = Winter sports.
languageNoThe user's language: de, en or tr (default en).
place_idYesplace_id from find_place.

Output Schema

NameRequiredDescriptionDefault
noteNo
textNo
placeYes
scopeNo
topicYes
sourceNo
websiteNo
has_knowledgeYes
response_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by identifying the content as curated/checked text and by defining the has_knowledge=false condition with a prescribed response ('say so, do not guess'). That is behavioral guidance an agent would otherwise have to infer from the output schema alone.

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?

Front-loaded with the usage trigger, then the resource definition, then the empty-result rule — a logical order with no filler. The colon-and-apposition construction in the first sentence is slightly dense but still parses cleanly.

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?

With an output schema present and annotations covering safety, the description supplies what structured fields cannot: when to reach for this tool versus hotel tools, and what to do when no checked text exists. Nothing essential is missing, though it doesn't hint at breadth or length of the returned knowledge text.

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 both enums are fully glossed in the schema, so the description need not restate topic or language meanings. It adds no syntax or constraint 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 specific verb and resource — retrieving hoteldiscount24's checked travel knowledge for a place and topic — and immediately scopes it against hotel content with 'the user asks about the destination itself rather than a hotel'. The concrete examples (best time to travel, climate per season) make the resource unmistakable versus get_hotel_facts or get_price_guide.

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

Usage Guidelines4/5

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

Gives a clear when-to-use trigger ('asks about the destination itself') and a when-not ('rather than a hotel'), plus explicit handling for the empty case: if has_knowledge=false, say so and do not guess. It stops short of naming the sibling to use instead for hotel questions, but the negative framing is strong enough to route the agent correctly.

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