Skip to main content
Glama

getecoback-climate-weather

duschset_halter_schon_vorhanden_angebotsumfang

Read-only

Bei einem Handbrausenangebot tatsächlichen Bedarf und zugesagten Lieferumfang des Halters getrennt ausweisen — Spot a duplicate holder or a missing item in a confirmed shower bundle.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vorhanden_halter": "<vorhanden_halter>",
      "vorhandener_halter_fuer_aufgabe": "<vorhandener_halter_fuer_aufgabe>",
      "angebot_halter": "<angebot_halter>",
      "artikelumfang_gleich": "<artikelumfang_gleich>"
    },
    "name": "duschset_halter_schon_vorhanden_angebotsumfang"
  }
}

Input Schema

NameRequiredDescriptionDefault
angebot_halterYesHalter im gekauften Angebot laut eindeutigem Lieferumfang.
vorhanden_halterYesFür den Zweck bereits vorgesehener Halter.
artikelumfang_gleichYesDie gewählte Option und die dokumentierte Lieferliste gehören exakt zum gleichen Angebot.
vorhandener_halter_fuer_aufgabeYesVorhandener Halter ist für die konkret gewünschte Brause und Nutzung vor Ort bestätigt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data and the description is not required to restate it. The description does add framing that this is a consistency check between two documented states rather than a lookup. However, for a tool with no output schema it says nothing about what comes back — a verdict, a diff, or a list of discrepancies — and nothing about how the four required inputs interact to produce that result.

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?

Two short sentences, front-loaded with the German statement of purpose followed by the English gloss. It is structurally clean and contains no filler, though the bilingual duplication means the same content is effectively delivered twice — modest redundancy for a short description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters, two enums, no output schema, and no nested objects, the tool is moderately complex. The description conveys the conceptual split well but leaves two gaps: what the return value looks like and how failing inputs (e.g. artikelumfang_gleich=false) affect the outcome. For a read-only classification tool with an existing safety annotation this is adequate but not complete.

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%, with per-parameter descriptions and enums for the two categorical inputs, so the schema carries the parameter burden. The description's 'tatsächlicher Bedarf' and 'zugesagter Lieferumfang' loosely map onto vorhanden_halter and angebot_halter, but it adds no interpretation of the enum values, no guidance on the two boolean confirmation flags, and no cross-parameter logic. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (Halter in a Handbrausenangebot) and the exact analytical split it performs: separating actual need from committed delivery scope. The added 'spot a duplicate holder or a missing item in a confirmed shower bundle' makes the intent concrete. It stops short of distinguishing itself from the many similarly named classification siblings (e.g. handbrause_halter_sitz_kopf_und_griff_beobachten), so no sibling routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied via the phrase 'in a confirmed shower bundle', which hints at the precondition that the bundle is confirmed. There is no explicit statement of when to call this versus the adjacent holder-observation tool, and no exclusion or prerequisite such as 'use only after artikelumfang_gleich is established'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources