Skip to main content
Glama

Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

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 (no commission) — 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

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoTOTAL 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_inNoOptional date YYYY-MM-DD; leave empty for the plain booking page
childrenNoAges of ALL children 0-17, comma-separated, e.g. '8,15'; empty if none. Ages change price and tourist tax (charged from age 17).
languageNoAnswer language: 'de' (default) or 'en' — use the language of the conversation. Text and card are always in the same language.de
apartmentNoApartment number such as '12' or '#16'; empty or 'all' = all online-bookable apartments; '17' = Studio #17 (on request only)
check_outNoOptional date YYYY-MM-DD; leave empty for the plain booking page

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
phoneNo
adultsNo
check_inNo
languageNo
check_outNo
child_agesNo
booking_urlNoBooking page on praegant.net, pre-filled when dates are given
inquiry_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • 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"
+}
  2. Changed7 schema fields changed
    • 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
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the readOnlyHint and destructiveHint annotations: it states the tool is read-only, performs no availability check, is instant, and never books/reserves/takes payment by design. It also specifies the return structure (text plus structuredContent with fields). This exceeds what annotations alone convey.

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?

The description is well-structured with purpose, usage, behavior, and return info clearly front-loaded. It is somewhat verbose but every sentence earns its place, explaining the non-commission model and the alternative tool. Minor redundancy exists (e.g., 'no commission' repeated), so it is not perfectly concise but is appropriately sized for the tool's complexity.

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?

Given the tool's complexity (6 params, 0 required, 100% schema coverage, output schema present), the description covers all necessary context: purpose, when to use, behavior, and return format. No critical information is missing for an agent to correctly select and invoke the tool.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description itself does not add new meaning to parameters beyond reiterating that dates are optional and prefilled; it doesn't expand on the detailed schema descriptions (e.g., adults total for groups, children age handling). Thus it adds minimal value over 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?

The description clearly states the tool builds a direct booking link on praegant.net with optional pre-fill, and distinguishes it from check_availability which already returns booking links. It is specific about the resource and action, leaving no ambiguity about what the tool does.

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?

Explicit when-to-use guidance is given: use when the guest has decided or wants to book without a price check. It also states when not to use it (when an availability result is at hand) and names the alternative (check_availability). This fully covers selection logic.

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