Das Landhaus Apartments Prägant

Get Booking Link

get_booking_link

Read-only

Build a direct booking link on praegant.net, optionally pre-filled with dates, party and apartment.

Use when the guest has decided and just wants the link, or wants to book without a price check. Bookings are always completed by the guest on praegant.net — this connector never books, reserves or takes payment by design. check_availability already returns a booking link per free apartment, so call this only when no availability result is at hand. Dates are optional (YYYY-MM-DD); without them the link opens the booking page. Behaviour: read-only, no availability check, instant. Returns text plus structuredContent (booking_url, inquiry_url, phone, email).

Input Schema

Name	Required	Description	Default
`adults`	No	TOTAL number of guests aged 18+ in the whole party — also for groups larger than one apartment (the tool plans the apartments). Guests aged 0-17 go into children.
`check_in`	No	Optional date YYYY-MM-DD; leave empty for the plain booking page
`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
`apartment`	No	Apartment number such as '12' or '#16'; empty or 'all' = all online-bookable apartments; '17' = Studio #17 (on request only)
`check_out`	No	Optional date YYYY-MM-DD; leave empty for the plain booking page

Output Schema

Name	Required	Description
`email`	No
`phone`	No
`adults`	No
`check_in`	No
`language`	No
`check_out`	No
`child_ages`	No
`on_request`	No	True = this apartment is enquiry only; there is no booking_url
`booking_url`	No	Booking page on praegant.net, pre-filled when dates are given
`inquiry_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / on_request

Added value: +{
+  "description": "True = this apartment is enquiry only; there is no booking_url",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

Changed7 schema fields changedSep 26, 2026

changedInput schema / properties / adults / description

Previous value: -"TOTAL adults (18+) of the whole party — also for groups larger than one apartment; the tool plans the apartments"New value: +"TOTAL number of guests aged 18+ in the whole party — also for groups larger than one apartment (the tool plans the apartments). Guests aged 0-17 go into children."

changedInput schema / properties / apartment / 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)"

addedInput schema / properties / check_in / description

Added value: +"Optional date YYYY-MM-DD; leave empty for the plain booking page"

addedInput schema / properties / check_out / description

Added value: +"Optional date YYYY-MM-DD; leave empty for the plain booking page"

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result of get_booking_link.",
+  "properties": {
+    "adults": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "booking_url": {
+      "description": "Booking page on praegant.net, pre-filled when dates are given",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "check_in": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "check_out": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "child_ages": {
+      "items": {
+        "type": "integer"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "email": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "inquiry_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "language": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "phone": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedSep 26, 2026

addedInput schema / properties / adults / description

Added value: +"TOTAL adults (18+) of the whole party — also for groups larger than one apartment; the tool plans the apartments"

addedInput schema / properties / adults / maximum
```
Added value: +30
```
addedInput schema / properties / adults / minimum
```
Added value: +1
```

addedInput schema / properties / apartment / description

Added value: +"Apartment number, e.g. '12' or '#16'; empty = all apartments"

addedInput schema / properties / children / description

Added value: +"Ages of ALL children 0–17, comma-separated, e.g. '8,15'. Empty if none. Ages matter for price and tourist tax."

addedInput schema / properties / language / description

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

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_booking_linkOutput",
-  "type": "object"
-}New value: +null

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes further: it explicitly disclaims booking, reserving and payment ('this connector never books, reserves or takes payment by design'), notes that no availability check occurs, that the operation is instant, and enumerates the returned fields. This is exactly the context annotations cannot express.

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 the purpose sentence, then usage, then behavior. Every sentence carries information, though the optional-dates caveat is stated twice (once in prose, once in the schema), a minor redundancy.

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?

An output schema exists, yet the description still names the key return fields; combined with the explicit no-booking disclaimer and the read-only/instant behavior note, an agent has everything needed to call this correctly instead of a heavier sibling.

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 coverage is 100%, so all six parameters are already documented in detail, including the empty-date fallback behavior. The description adds the grouping 'dates, party and apartment' and restates that dates are optional in YYYY-MM-DD, which largely duplicates the schema. 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?

States a specific verb and resource: 'Build a direct booking link on praegant.net, optionally pre-filled with dates, party and apartment.' Scope and output are unambiguous, and the sibling distinction from check_availability is made explicit in the same description.

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 both when-to-use ('guest has decided and just wants the link, or wants to book without a price check') and when-not ('call this only when no availability result is at hand'), and names the alternative sibling check_availability with the reason it already supersedes this tool.

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?