Skip to main content
Glama

getecoback-climate-weather

handbrause_angebot_verwechslung_kopfbrause_bauart

Read-only

Ein ähnlich benanntes Brausenangebot anhand der technischen Bauart von der gewünschten Handbrause trennen — Keep an overhead-shower listing out of a hand-shower shortlist.

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": {
      "gesucht": "<gesucht>",
      "angebot_beschriftet": "<angebot_beschriftet>",
      "selbe_artikelnummer": "<selbe_artikelnummer>",
      "typ_nur_im_serienbild": "<typ_nur_im_serienbild>"
    },
    "name": "handbrause_angebot_verwechslung_kopfbrause_bauart"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesuchtYesTatsächlich vorgesehene Geräteart.
angebot_beschriftetYesBauart in der eindeutigen Herstellerunterlage zum Angebot.
selbe_artikelnummerYesDie Händlerauswahl und die technische Unterlage bezeichnen nachweislich denselben Artikel.
typ_nur_im_serienbildYesEin Serien- oder Umgebungsbild zeigt eine weitere Bauart, deren Aufnahme im Angebot ungeklärt ist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered, and the description adds the judgment criterion (technical Bauart, not the listing name). It does not disclose what the call produces — a verdict, a boolean, or an explanation — which matters for a pure classification tool with no output schema.

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?

One front-loaded German sentence with the practical consequence attached, zero filler. The bilingual em-dash gloss restates the same content, which is mild redundancy but aids recall rather than obscuring anything.

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?

All four parameters are required and the description conveys the discrimination intent, but with no output schema it leaves the result of the decision (and how conflicting inputs such as typ_nur_im_serienbild=true resolve) unexplained. Adequate to invoke, insufficient to predict the outcome.

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% and both enum parameters carry their own descriptions, so the schema does the heavy lifting. The description reinforces the Bauart-based logic but adds no syntax, ordering, or combination rules beyond what the fields already state; 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 a specific operation ("anhand der technischen Bauart ... trennen") on a specific resource ("ähnlich benanntes Brausenangebot") and states the discriminating criterion. It is clearly not the same as observational siblings like handbrause_halter_sitz_kopf_und_griff_beobachten, but it never names an alternative tool, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

The concrete scenario is spelled out: keep an overhead-shower listing out of a hand-shower shortlist, which tells an agent exactly when this tool applies. Missing are explicit when-not conditions or a pointer to the sibling that handles the non-conflicting case.

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