Skip to main content
Glama
Sign In

Das Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

Get Apartment Details

get_apartment_details
Read-only

Describe one or all apartments: size, bedrooms, maximum guests, description and page link.

Use for questions about the apartments themselves ("how big is #16?", "which apartment has 2 bedrooms?", "which apartments fit 5 people?"). It contains no prices or availability — use check_availability for dates and prices, or get_rates for a month overview. Studio #17 is only listed when asked for by number and is marked as bookable on request. Visual version with photos: render_apartment_gallery. Behaviour: read-only; facts as maintained on praegant.net (synced hourly), answers in milliseconds. Returns text plus structuredContent.apartments (nr, name, m2, bedrooms, max_guests, description, url, on_request, images, and where maintained: beds, outdoor, notes, recommended_for). An unknown number returns the list of existing apartment numbers.

Input Schema

NameRequiredDescriptionDefault
nameNoApartment number such as '12' or '#16'; empty or 'all' = all online-bookable apartments; '17' = Studio #17 (on request only)
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
languageNo
apartmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  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 / name / description
      Previous value: -"Apartment number, e.g. '12' or '#16'; empty = all apartments"New value: +"Apartment number such as '12' or '#16'; empty or 'all' = all online-bookable apartments; '17' = Studio #17 (on request only)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ApartmentInfo": {
+      "properties": {
+        "bedrooms": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "description": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "images": {
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "m2": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "max_guests": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nr": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on_request": {
+          "description": "True = not bookable online, enquiry only",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "photos": {
+          "description": "JPEG data URIs (render tool only)",
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Apartment page, or the enquiry form for on-request apartments",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "description": "Result of get_apartment_details / render_apartment_gallery.",
+  "properties": {
+    "apartments": {
+      "items": {
+        "$ref": "#/$defs/ApartmentInfo"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "language": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / language / description
      Added value: +"'de' (default) or 'en' — the language of the conversation"
    • addedInput schema / properties / name / description
      Added value: +"Apartment number, e.g. '12' or '#16'; empty = all apartments"
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable operational context: facts are synced hourly from praegant.net, answers are returned in milliseconds, Studio #17 is only listed when asked for by number and marked bookable on request, and unknown numbers return the list of existing apartment numbers.

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 description is front-loaded with purpose, then moves efficiently through use cases, alternatives, special-case handling, visual equivalent, behavioral guarantees, return shape, and unknown-number behavior. It is dense but every sentence supplies routing or behavioral value.

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, so return values need not be fully explained, yet the description still summarizes structuredContent.apartments and covers data freshness, latency, alternatives, and edge cases. For a two-parameter read-only lookup tool, nothing important is missing.

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 coverage is 100%, so the structured parameter descriptions already do most of the work. The description still adds meaning beyond the schema by explaining 'all' vs '#17' behavior and the unknown-number fallback, though it does not add much about the 'language' parameter beyond what the schema already states.

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 ('Describe') and resource ('apartments'), enumerates the returned facts (size, bedrooms, max guests, description, page link), and explicitly distinguishes itself from check_availability, get_rates, and render_apartment_gallery. An agent can tell exactly what this tool does and which sibling to use for prices or visuals.

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?

Provides concrete example questions ('how big is #16?', 'which apartments fit 5 people?'), states it contains no prices or availability, and routes date/price questions to check_availability and month overviews to get_rates. It also calls out the Studio #17 on-request-only exception, leaving little to inference.

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