Skip to main content
Glama
Sign In

Das Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

Get Region Information

get_region_info
Read-only

Return curated information about Bad Kleinkirchheim and the house for a topic.

Use for "what can we do there?" and house questions: house rules and services (self-catering, no breakfast, bread-roll service, no pets, baby cot/high chair on request, chip access), skiing (winter), hiking, biking and lakes (summer), thermal spas and the in-house sauna (wellness), golf incl. the free green fee and tee-time booking, families, workation, arrival. The Kärnten Card (summer only) and the free green fee are explained exactly. Not for prices or availability (check_availability) and not for apartment facts (get_apartment_details). Behaviour: read-only, static curated content from the property (no web search), instant; topics 'house' and 'wellness' also list the property's official house photos (sauna, steam bath, relaxation room …) — to show them, call render_house_photos, never a web image search (other businesses share the 'Prägant' name). Returns text plus structuredContent.topics (topic, lines), photos (kind, url, caption) and contact details.

Input Schema

NameRequiredDescriptionDefault
topicNoOne of house (self-catering, bread rolls, pets, baby cot, chip access), winter, summer, wellness, golf, family, workation, arrival (aliases like 'ski', 'hund', 'breakfast', 'anreise' work); empty = overview
languageNoAnswer language: 'de' (default) or 'en' — use the language of the conversation. Text and card are always in the same language.de

Output Schema

NameRequiredDescriptionDefault
emailNo
phoneNo
topicsNoSections: topic, lines
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / description
      Previous value: -"Result of get_region_info."New value: +"Result of get_region_info / render_house_photos."
  2. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"One of winter, summer, wellness, golf, family, workation, arrival (aliases like 'ski', 'wandern', 'anreise' work); empty = overview"New value: +"One of house (self-catering, bread rolls, pets, baby cot, chip access), winter, summer, wellness, golf, family, workation, arrival (aliases like 'ski', 'hund', 'breakfast', 'anreise' work); empty = overview"
    • addedInput schema / properties / topic / examples
      Added value: +[
+  "house",
+  "golf",
+  "winter"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"'de' (default) or 'en' — the language of the conversation"New value: +"Answer language: 'de' (default) or 'en' — use the language of the conversation. Text and card are always in the same language."
    • changedInput schema / properties / topic / description
      Previous value: -"winter, summer, wellness, golf, family, workation, arrival — empty for an overview"New value: +"One of winter, summer, wellness, golf, family, workation, arrival (aliases like 'ski', 'wandern', 'anreise' work); empty = overview"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Result of get_region_info.",
+  "properties": {
+    "email": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "language": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "phone": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topics": {
+      "description": "Sections: topic, lines",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  4. Changed3 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
+  "default": "de",
+  "description": "'de' (default) or 'en' — the language of the conversation",
+  "title": "Language",
+  "type": "string"
+}
    • addedInput schema / properties / topic / description
      Added value: +"winter, summer, wellness, golf, family, workation, arrival — empty for an overview"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_region_infoOutput",
-  "type": "object"
-}New value: +null
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already declare read-only, non-destructive, closed-world behavior, and the description adds substantial context beyond that: static curated content, no web search, instant response, photo behavior for 'house' and 'wellness', and the shape of returned text plus structuredContent. These details are consistent with the annotations and materially help invocation.

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?

The description is front-loaded with purpose and usage, then proceeds to behavior and return details, so an agent can stop reading early if needed. It is somewhat long due to the full topic inventory, but the detail is mostly useful rather than redundant.

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?

Given the annotations, output schema, and sibling tools, the description is complete enough to call correctly. It covers when to use it, when not to, photo rendering behavior, and what the response contains, leaving no major gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaningful topic semantics by explaining what categories like house services, skiing, wellness, golf, and arrival cover. It does not describe the language parameter, but the schema already handles that fully.

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?

The description states a specific verb and resource: returning curated information about Bad Kleinkirchheim and the house for a topic. It explicitly distinguishes itself from sibling tools check_availability and get_apartment_details, so an agent can select it without opening other schemas.

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?

It names concrete use cases such as 'what can we do there?' and house questions, then explicitly excludes prices/availability and apartment facts while pointing to the correct alternatives. It also gives a specific workflow for showing house photos via render_house_photos rather than a web image search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Das Landhaus Apartments Prägant toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources