Skip to main content
Glama

getecoback-climate-weather

wasserkocher_twk8613p_360_sockel_originalbasis

Read-only

Prüft, ob der angebotene 360-Grad-Sockel für den konkreten Bosch-Wasserkocher tatsächlich als mitgelieferte Basis belegt ist — Check original kettle-base evidence without assuming cross-model interchangeability.

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": {
      "anleitung_zugeordnet": "<anleitung_zugeordnet>",
      "basis": "<basis>",
      "nur_360_kennzeichnung": "<nur_360_kennzeichnung>"
    },
    "name": "wasserkocher_twk8613p_360_sockel_originalbasis"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisYesVorliegende Herkunft der Basis.
anleitung_zugeordnetYesDas Gerät ist als deutsches TWK8613P identifiziert und die angegebene TWK86-Anleitung über die E-Nummer zugeordnet.
nur_360_kennzeichnungYesDie einzige Zusatzangabe am Fremdteil ist die 360-Grad-Beschreibung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe, closed-world read, so the description need not restate safety. It does add a genuine behavioural stance — the check is evidence-based and explicitly refuses to infer cross-model compatibility — but it never says what the verdict looks like or how an 'offen'/'nicht_vorhanden' case is reported.

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?

A single front-loaded sentence with the checking action first and the anti-assumption constraint second; the bilingual restatement sharpens rather than pads the claim, and there is no wasted wording.

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?

For a three-parameter read-only verification tool with full schema coverage, the description covers what is checked and the key caveat. With no output schema, however, it leaves the shape of the result (a verdict derived from the inputs) unexplained, which is the remaining gap for an agent deciding whether to rely on the answer.

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 enum values are individually documented, so the schema carries the parameter burden. The description adds no meaning about the three inputs beyond the evidence framing already implied by the purpose; 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 states a specific verb and object: it 'Prüft' whether the offered 360-degree base is documented as the included base for this concrete Bosch kettle. The added clause 'without assuming cross-model interchangeability' carves out a scope distinct from behavioural siblings such as the boil/restart or descaling tools, though it does not name a specific alternative.

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 implied rather than stated: the tool applies when establishing provenance of the base, and the caution against assuming cross-model interchangeability signals when a negative or uncertain verdict matters. There is no explicit when-to-use/when-not-to-use framing or named alternative among the many base-related siblings (e.g. the dishwasher-base or condensation-base tools).

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