Skip to main content
Glama

Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

Get Offers

get_offers
Read-only

List all current seasonal offers and packages published on praegant.net.

Use when the guest asks about deals, packages or what is special in a season, independent of dates. When the guest already has dates, check_availability includes only the offers valid for that stay — no need to call both. Visual version: render_offers_card. Behaviour: read-only; offers as published on the website (synced hourly, expired ones removed). Returns text plus structuredContent.offers (title, valid_from, valid_to, price_text, summary, url).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
offersNotitle, valid_from, valid_to, price_text, summary, season, url, includes, image
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Result of get_offers / render_offers_card.",
+  "properties": {
+    "language": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "offers": {
+      "description": "title, valid_from, valid_to, price_text, summary, season, url, includes, image",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / language / description
      Added value: +"'de' (default) or 'en' — the language of the conversation"
  3. First observed

TDQS

A4.7/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, and the description reinforces read-only behavior while adding genuinely useful context: offers are synced hourly, expired ones are removed, and the response includes text plus structuredContent.offers with specific fields. This goes beyond what annotations alone provide.

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 and well-structured: purpose first, then usage guidance, then behavior and return shape. Every sentence contributes useful information, and the sibling routing is packed into a few clear lines without 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?

For a simple read-only tool with one optional parameter, an output schema, and strong annotations, the description is complete. It covers when to use it, when not to, what it returns, and how it behaves in terms of freshness and filtering. Nothing an agent needs to invoke it correctly 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% and the single optional language parameter is fully documented in the schema, including the instruction to match the conversation language. The tool description adds no additional parameter-level meaning, so the baseline of 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?

The description opens with a specific verb and resource: 'List all current seasonal offers and packages published on praegant.net.' It clearly distinguishes this tool from siblings by framing it as the date-independent offers listing, while check_availability and render_offers_card are explicitly named as alternatives.

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?

The description gives explicit when-to-use guidance: use when the guest asks about deals, packages, or seasonal specials independent of dates. It also gives a when-not-to-use rule: if the guest already has dates, check_availability covers valid offers and there is no need to call both. It even names the visual alternative render_offers_card.

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