Landhaus Apartments Prägant

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). An unknown number returns the list of existing apartment numbers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Apartment number such as '12' or '#16'; empty or 'all' = all online-bookable apartments; '17' = Studio #17 (on request only)
`language`	No	Answer 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

Name	Required	Description	Default
`language`	No
`apartments`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 26, 2026

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"
+}

Changed2 schema fields changedSep 26, 2026

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"

First observedSep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses the data source (praegant.net), sync frequency (hourly), response speed, and the fallback behavior for unknown numbers (returns list of existing apartment numbers). These are meaningful behavioral traits not present in the structured annotations.

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 dense but every sentence serves a purpose: function, usage examples, exclusions/alternatives, special case, behavior, and return format. It is front-loaded with the main purpose and flows logically to edge cases, with no filler or tautology.

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?

For a tool with two optional parameters, an output schema, and safety annotations, the description covers all necessary context: what it does, when to use it, behavior, output structure, and edge cases (unknown number, Studio #17). There are no significant gaps that would prevent an agent from using it correctly.

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?

Both parameters are fully documented in the schema (100% coverage), including the special value '17' and the language guidance. The description restates some of this but adds little new param-level meaning; it mainly reinforces what the schema already says. The return-shape info belongs to output, not parameter semantics, so 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?

The description opens with a specific verb and resource ('Describe one or all apartments') and enumerates the exact fields returned (size, bedrooms, max guests, description, page link). It clearly differentiates from siblings by explicitly stating it contains no prices/availability and pointing to check_availability, get_rates, and render_apartment_gallery.

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?

Usage guidance is explicit: it gives example questions, states what the tool does NOT cover (prices/availability), and names the correct alternatives for those cases. It also covers the special case of Studio #17 and the visual gallery variant, leaving no ambiguity about when to choose this tool.

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 tools Inspect

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

Need Help?