Das Landhaus Apartments Prägant

Show Rates Card

render_rates_card

Read-only

Show a month's prices and booking rules as an interactive card in the chat.

Use instead of get_rates when the guest wants to see the overview; each apartment line can be tapped to check its dates. Use get_rates when only the data is needed. Same arguments, behaviour (read-only, live) and result as get_rates.

Input Schema

Name	Required	Description	Default
`month`	No	Month as '2027-07', 'July', 'Juli 2027'; empty = next month
`adults`	No	Adults sharing one apartment (1-5)
`guests`	No	Deprecated alias of adults (clients before 2.2.0); 0 = unused
`children`	No	Ages of ALL children 0-17, comma-separated, e.g. '8,15'; empty if none. Ages change price and tourist tax (charged from age 17).
`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

Name	Required	Description
`month`	No	YYYY-MM
`perks`	No
`weeks`	No	Searched reference stays with all prices
`adults`	No
`offers`	No
`status`	No	ok, closed, fully_booked or not_released
`periods`	No	Booking rules: from, to, closed, min_nights, arrival_weekdays
`language`	No
`apartments`	No	Per apartment: nr, name, lowest total EUR, nights, check_in/check_out of that reference stay
`child_ages`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed6 schema fields changedSep 26, 2026

changedInput schema / properties / adults / description

Previous value: -"Adults in one apartment"New value: +"Adults sharing one apartment (1-5)"

changedInput schema / properties / children / description

Previous value: -"Ages of ALL children 0–17, comma-separated, e.g. '8,15'. Empty if none. Ages matter for price and tourist tax."New value: +"Ages of ALL children 0-17, comma-separated, e.g. '8,15'; empty if none. Ages change price and tourist tax (charged from age 17)."

changedInput schema / properties / guests / description

Previous value: -"Deprecated alias of adults (clients before 2.2.0)"New value: +"Deprecated alias of adults (clients before 2.2.0); 0 = unused"

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 / month / description

Previous value: -"e.g. '2027-07', 'July', 'Juli 2027'; empty = next month"New value: +"Month as '2027-07', 'July', 'Juli 2027'; empty = next month"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result of get_rates / render_rates_card.",
+  "properties": {
+    "adults": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "apartments": {
+      "description": "Per apartment: nr, name, lowest total EUR, nights, check_in/check_out of that reference stay",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "child_ages": {
+      "items": {
+        "type": "integer"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "language": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "month": {
+      "description": "YYYY-MM",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "offers": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "periods": {
+      "description": "Booking rules: from, to, closed, min_nights, arrival_weekdays",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "perks": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "ok, closed, fully_booked or not_released",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "weeks": {
+      "description": "Searched reference stays with all prices",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed8 schema fields changedSep 26, 2026

addedInput schema / properties / adults

Added value: +{
+  "default": 2,
+  "description": "Adults in one apartment",
+  "maximum": 5,
+  "minimum": 1,
+  "title": "Adults",
+  "type": "integer"
+}

addedInput schema / properties / children

Added value: +{
+  "default": "",
+  "description": "Ages of ALL children 0–17, comma-separated, e.g. '8,15'. Empty if none. Ages matter for price and tourist tax.",
+  "title": "Children",
+  "type": "string"
+}

changedInput schema / properties / guests / default
```
Previous value: -2New value: +0
```

addedInput schema / properties / guests / description

Added value: +"Deprecated alias of adults (clients before 2.2.0)"

addedInput schema / properties / guests / maximum
```
Added value: +5
```
addedInput schema / properties / guests / minimum
```
Added value: +0
```

addedInput schema / properties / language / description

Added value: +"'de' (default) or 'en' — the language of the conversation"

addedInput schema / properties / month / description

Added value: +"e.g. '2027-07', 'July', 'Juli 2027'; empty = next month"

First observedSep 23, 2026

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, and the description reinforces them while adding genuinely new context: the data is live, the card is interactive with tappable apartment lines, and behaviour/result are identical to get_rates. It stops short of noting any fallback when a client cannot render cards, which is the one behavioral gap left.

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?

Two short paragraphs, the primary purpose front-loaded in the first sentence, and the routing rule in the second. No filler; every clause either states the purpose, the alternative, or the behavioural equivalence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and full parameter documentation mean the description needn't explain return values, and annotations cover the safety profile. It is nearly complete for a 5-param rendering tool; only an edge case such as non-card-capable clients is unaddressed.

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%, including formats for month, the children age semantics, and the deprecated guests alias, so the schema does the heavy lifting. The description only adds the cross-reference 'same arguments as get_rates', which is a convenience pointer rather than new 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 and resource ('Show a month's prices and booking rules as an interactive card') and immediately delimits it from the sibling get_rates. An agent can tell the rendering tool apart from the data tool without opening either 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 names the alternative and the condition that selects it: use this when the guest wants the overview with tappable apartment lines, use get_rates when only the data is needed. Both the when and the when-not are stated.

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 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?