Skip to main content
Glama

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
languageNo
apartmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'read-only, no prices.' It adds useful behavioral context beyond annotations: the swipeable photo counts, buttons for availability/page access, and the fact that the result matches get_apartment_details plus photos.

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?

Compact and front-loaded: the first sentence says what the tool does, and the second sentence provides the selection rule. Every sentence earns its place with no redundant detail.

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 a full input schema, an output schema, and safety annotations present, the description adds the missing decision context: when to use it, what the gallery shows, and how it differs from get_apartment_details. Nothing needed for correct invocation 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 the schema already fully documents both parameters. The description adds only broad context ('Same arguments') and the one/all semantics, which are already reflected in the schema. This meets the baseline but does not substantially enrich parameter meaning.

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 ('Show') plus resource ('one or all apartments with photos') and the output format ('interactive gallery card'). The description explicitly contrasts with get_apartment_details by adding photos, so the tool is clearly differentiated from its siblings.

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?

Gives explicit routing guidance: 'Use instead of get_apartment_details when the guest wants to see the apartments' and clarifies the one-apartment vs all-apartments photo behavior. This leaves no ambiguity about when to choose this tool over the nearest alternative.

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