Skip to main content
Glama

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. Returns text plus structuredContent.topics (topic, lines) and contact details.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
phoneNo
topicsNoSections: topic, lines
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+}
  3. 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
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint=false, but the description adds genuinely non-structured context: static curated content from the property, no web search, instant response. Slightly redundant given an output schema exists, but the 'no web search' guarantee is behavior an agent cannot infer from annotations.

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 core purpose and routing exclusions, but the long inline enumeration of house services and domains is verbose and partially duplicates the schema's topic list. Efficient in intent, mildly over-long in execution.

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?

Output schema exists, so the return-format sentence is bonus rather than necessity; annotations cover safety; both parameters are fully documented in the schema. Nothing an agent needs to call this correctly is missing.

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 the schema already lists allowed topics, aliases, empty=overview, and the language default/behavior. The description's topic enumeration largely repeats the schema, so it adds little beyond what is already structured. Baseline 3 is appropriate.

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 ('Return curated information about Bad Kleinkirchheim and the house for a topic') and immediately scopes it against siblings by name. An agent can distinguish this from check_availability and get_apartment_details without opening a 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?

Explicitly lists when to use it ('what can we do there?' and house questions, with enumerated topic domains) and when not to ('Not for prices or availability (check_availability) and not for apartment facts (get_apartment_details)'). Both the alternative tools and the selecting condition are named.

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

All 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