Skip to main content
Glama
Sign In

Das Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

Show Apartment Gallery

render_apartment_gallery
Read-only

Show one or all apartments with photos as an interactive gallery card in the chat.

Use instead of get_apartment_details when the guest wants to see the apartments (one apartment: up to 3 swipeable photos; all: one photo each, with buttons to check availability or open the page). Same arguments, behaviour (read-only, no prices) and result as get_apartment_details, plus photos. The card already shows the official photos — do not add images from a web search (other rentals share the 'Prägant' name).

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, yet the description still adds real context: no prices are shown, arguments and result mirror get_apartment_details, and the card is pre-populated with official photos so external images must not be injected. It stops short of describing failure modes or what happens for unlisted apartments, so it is strong but not exhaustive.

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 purpose, then differentiation, then constraint — a logical order with no filler. The 'read-only' restatement duplicates the annotations and the 'Prägant' parenthetical is dense, but both still serve a purpose.

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?

With an output schema present, return values need not be documented, yet the description still summarizes the card contents and buttons. For a zero-required-parameter rendering tool with full schema coverage and annotations, nothing an agent needs in order to invoke it 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%, so both parameters (name, language) are already fully documented, including the 'all'/empty and '17' cases; baseline 3 applies. The description adds only that the name selection maps to different photo counts per branch, which is marginal beyond the schema.

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 concrete verb and resource ('show one or all apartments with photos as an interactive gallery card in the chat') and explicitly distinguishes itself from the sibling get_apartment_details. The per-branch rendering difference (one apartment = up to 3 swipeable photos; all = one photo each with action buttons) makes the tool's identity unambiguous.

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 names the alternative and the selection condition: 'Use instead of get_apartment_details when the guest wants to see the apartments.' It also gives a negative instruction (do not source images from web search, since other rentals share the 'Prägant' name), which is a genuine when-not rule rather than vague context.

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