Skip to main content
Glama

Landhaus Apartments Prägant

by net.praegant
OverviewDiscussionsAdmin

Show Offers Card

render_offers_card
Read-only

Show the current website offers as an interactive card with photos and links.

Use instead of get_offers when the guest wants to browse the offers visually. Same behaviour (read-only) and result as get_offers, plus a photo per offer.

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.5/5.0
Behavior4/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 this by stating the tool is read-only. It adds useful behavioral context by explaining the result is identical to get_offers plus a photo per offer, and that the output is an interactive card, which goes beyond the structured annotation fields.

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 two concise sentences with no filler. The first sentence states the core purpose, and the second immediately provides usage guidance and sibling differentiation, making it easy to scan.

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 single optional parameter, full schema coverage, read-only annotations, and explicit comparison to get_offers, the description covers everything needed to select and invoke the tool correctly. The presence of an output schema also means the description does not need to explain return values.

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 schema has 100% coverage for its single optional parameter, with a clear description of the 'language' field and its default. The description adds no parameter-level details beyond the schema, but the schema already carries the full burden, so a baseline score 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 names a specific verb ('Show'), a concrete resource ('current website offers'), and the output form ('interactive card with photos and links'). It explicitly distinguishes itself from the sibling tool get_offers by the visual presentation, so an agent can tell them apart without opening the 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?

The description explicitly says 'Use instead of get_offers when the guest wants to browse the offers visually' and clarifies that behavior and result match get_offers plus a photo. This gives clear selection criteria against the main sibling and leaves no ambiguity about when to invoke it.

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