Landhaus Apartments Prägant

Get Rates

get_rates

Read-only

Get the price level of each apartment for a whole month plus that month's booking rules.

Use when the guest has no exact dates yet ("what does a week in July cost?", "when is it cheapest?"). For each apartment it returns the lowest total price of a real reference stay in that month (usually 7 nights, incl. final cleaning and tourist tax) and the arrival days / minimum stay / closures of the month. Not for exact prices on specific dates — use check_availability for that. Visual version: render_rates_card with the same arguments. Behaviour: read-only, live from the booking system (about 1-2 s, cached 5 min). Returns text plus structuredContent (apartments, periods, weeks, perks, offers).

Input Schema

TableJSON 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

TableJSON 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.

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.7/5.0

Behavior5/5

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

Annotations already mark it read-only and non-destructive, and the description adds valuable behavior: live from the booking system, 1-2 seconds latency, 5-minute cache, and returns text plus structuredContent. This goes beyond the annotations and gives the agent realistic operational expectations.

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 compact yet complete: purpose, usage context, exclusion, alternative, behavior, and return format are all covered in a few sentences. Every sentence earns its place and the most important purpose is front-loaded.

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 read-only lookup tool with zero required parameters and an output schema, this description fully covers what the tool does, when to use it, what it returns, and how it behaves operationally. Nothing critical 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 documents all five parameters. The description does not need to add parameter-level meaning, though it does helpfully clarify that the returned price is for a reference stay with final cleaning and tourist tax.

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 states a specific verb and resource: get the price level of each apartment for a whole month plus booking rules. It also clearly distinguishes itself from check_availability and render_rates_card, so an agent can differentiate it from 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?

Explicitly says when to use it ('when the guest has no exact dates yet'), when not to use it ('Not for exact prices on specific dates'), which sibling to use instead (check_availability), and that render_rates_card is the visual version with the same arguments.

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?