Skip to main content
Glama

getecoback-climate-weather

braun_wk3000_45sekunden_pruefmenge_bezug

Read-only

Prüfe, ob die Braun-Angabe von 45 Sekunden zur eigenen gemessenen Wassermenge passt — Scope the Braun 45-second claim to its documented water quantity

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": {
      "wk3000bk": "<wk3000bk>",
      "versuch_ml": "<versuch_ml>",
      "versuch_s": "<versuch_s>",
      "gleiche_messbedingung": "<gleiche_messbedingung>"
    },
    "name": "braun_wk3000_45sekunden_pruefmenge_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
wk3000bkYesBraun PurEase WK 3000 BK mit Referenz WK304AI-WK3000BK bestätigt
versuch_sYesBeobachtete Sekunden bis zum gewählten Ende
versuch_mlYesBei der eigenen Messung tatsächlich aufgeheizte Wassermenge
gleiche_messbedingungYesAnfangstemperatur, Messstart und Ende sind nach Vorgabe ausreichend vergleichbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, which the description does not extend. It never says what the check produces (no output schema exists), whether there is a tolerance band around 45 seconds, or how an incomparable measurement is reported. The 'documented water quantity' scoping is the only added behavioral hint.

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?

A single compact sentence with the core check front-loaded. The bilingual duplication repeats the same idea twice, which costs a little space without adding information.

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

Completeness2/5

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

This is a four-required-parameter verification tool with no output schema, so the description should at minimum say what a passing/failing result looks like and how the 45-second benchmark is scaled to the measured volume. Neither is present, leaving the agent unable to predict the response.

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 all four parameters are already documented, including the WK304AI-WK3000BK reference and the comparison-of-conditions flag. The description mentions the water quantity and the 45-second figure but adds no format, range, or edge-case guidance 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 names a specific action and object: check whether the Braun 45-second claim fits one's own measured water quantity. The English clause ('scope the Braun 45-second claim to its documented water quantity') reinforces the resource, but the verb 'scope' is vaguer than the German 'Prüfe' and there is no differentiation from any sibling tool.

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: an agent can infer the tool applies when reconciling a manufacturer's 45-second figure against its own measurement. There is no statement of when to prefer this over alternatives, no preconditions, and no note on what to do if the conditions are not comparable.

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