Skip to main content
Glama

getecoback-climate-weather

wasserkocher_tassenmarke_messbecher

Read-only

Praktische Tassenanzeige mit zwei gemessenen Kaltwasserfüllungen prüfen — Compare a kettle’s cup mark against the volume of your serving cup.

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": {
      "linie_ml": "<linie_ml>",
      "tasse_ml": "<tasse_ml>",
      "messspanne_ml": "<messspanne_ml>"
    },
    "name": "wasserkocher_tassenmarke_messbecher"
  }
}

Input Schema

NameRequiredDescriptionDefault
linie_mlYesMit Messbecher abgelesene Kaltwassermenge an der ausgewählten Kannenmarke.
tasse_mlYesAm gewünschten Pegel mit Messbecher bestimmte Tassenfüllung.
messspanne_mlYesGeschätzte gesamte Unsicherheit beider abgelesenen Mengen zusammen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description does add that two independently measured cold-water fills are compared and that measurement uncertainty is part of the input picture, but it never says what the verdict looks like (a ratio, a pass/fail, a corrected cup count) — relevant because there is 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, but they are a German/English restatement of the same idea rather than a progression, and the German half leads with vague praise ('Praktische Tassenanzeige') instead of the operation. Nothing is grossly padded, but the front-loading is weak and the dual-language duplication costs 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?

A three-parameter computation with no output schema needs the description to say what comes back and how to read it; this one does not. The only real signal an agent gets is that the result relates a kettle mark to a cup volume, with no indication of direction, units, or interpretation of the uncertainty input.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with an explicit German description for each of the three parameters, so the schema already does the semantic work and the baseline of 3 applies. The description adds a bit by framing linie_ml and tasse_ml as two measured fills that are compared, but it does not explain the role of messspanne_ml (the combined estimated uncertainty), which is the least intuitive parameter.

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

Purpose3/5

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

The verb 'prüfen'/'compare' and the objects (kettle cup mark vs. serving-cup volume) are named, so the general intent is recoverable. But the core question the tool answers — does the mark match your cup, how many cups does the mark yield, or is the deviation acceptable — is never stated, and the German clause about 'zwei gemessenen Kaltwasserfüllungen' is cryptic without the schema.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool, no prerequisite (e.g. take two cold-water measurements first), and no mention of what would make a sibling such as wasserkocher_mehrmenge_szenario or wasserkocher_wahlstufe_abgleichen the better choice. The agent must infer the scenario entirely from the name.

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