Skip to main content
Glama

getecoback-climate-weather

duschhalter_bohrfrei_befestigungsart_beleg

Read-only

Ein Angebot mit der Angabe bohrfrei auf eindeutig dokumentierte Befestigungsart und eigene Vorgaben prüfen — Distinguish suction, adhesive and clamp claims before buying.

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": {
      "art": "<art>",
      "artikelbezug_belegt": "<artikelbezug_belegt>",
      "saugnapf_erlaubt": "<saugnapf_erlaubt>",
      "klebepad_erlaubt": "<klebepad_erlaubt>",
      "klemme_erlaubt": "<klemme_erlaubt>",
      "schraube_erlaubt": "<schraube_erlaubt>"
    },
    "name": "duschhalter_bohrfrei_befestigungsart_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesBefestigungsart aus der zugeordneten technischen Unterlage.
klemme_erlaubtYesKlemme gehört zu den bestätigten Möglichkeiten.
klebepad_erlaubtYesKlebepad gehört zu den bestätigten Möglichkeiten.
saugnapf_erlaubtYesSaugnapf gehört laut eigener bestätigter Vorgabe zu den möglichen Befestigungsarten.
schraube_erlaubtYesSchraube gehört zu den bestätigten Möglichkeiten.
artikelbezug_belegtYesDie Unterlage gehört nachweislich zum genauen angebotenen Halter.

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 agent knows this is a safe, non-mutating check. The description adds no behavior beyond that: it does not say what the check returns, how a 'bohrfrei' claim without documentation is treated, or how the 'unbekannt' enum value is handled. Given annotation coverage, a 3 is appropriate.

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 clauses, no filler, and the verification intent is front-loaded. The bilingual split is slightly awkward but not pure duplication, since the English half names the three mounting types the German half leaves implicit.

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 six required parameters and no output schema, the description should at least indicate what kind of verdict is produced or how conflicting evidence and 'unbekannt' are resolved. It covers the input side ('eigene Vorgaben' maps loosely to the *_erlaubt flags) but leaves the result semantics entirely unstated.

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%, so the baseline is 3. The description echoes the suction/adhesive/clamp concepts, which partly maps to the 'saugnapf_erlaubt', 'klebepad_erlaubt' and 'klemme_erlaubt' flags, but it omits screw and 'artikelbezug_belegt' and adds no interpretation beyond the schema.

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 states a concrete verb and object: it checks ('prüfen') a drill-free ('bohrfrei') claim in an offer against a documented mounting type and the user's own requirements, and names the three claim types to distinguish. That is clear enough to select the tool, but it never differentiates itself from the many sibling '*_beleg' verification tools, so it stays at 4.

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?

'before buying' gives one usage occasion, implicitly checking a listing prior to purchase. There is no explicit when-not guidance, no prerequisites (e.g. what to do when the technical document is missing), and no mention of any sibling alternative.

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