Skip to main content
Glama

getecoback-climate-weather

fenstersauger_messaufgabe_mulde_einzweck

Read-only

Eine Messprobe mit Wasser aus Glasfläche und Gerätepflege nach Quelle auftrennen — Keep rinse water out of the suction performance measurement.

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": {
      "sammelgesamt_ml": "<sammelgesamt_ml>",
      "vorher_im_tank_ml": "<vorher_im_tank_ml>",
      "pflege_ml": "<pflege_ml>",
      "zeitfenster_getrennt": "<zeitfenster_getrennt>"
    },
    "name": "fenstersauger_messaufgabe_mulde_einzweck"
  }
}

Input Schema

NameRequiredDescriptionDefault
pflege_mlYesBeim anschließenden, dokumentierten Pflegeschritt zusätzlich erfasste Menge.
sammelgesamt_mlYesGemessene Flüssigkeit über den ganzen Ablauf.
vorher_im_tank_mlYesBeim Start bestätigte bereits enthaltene Flüssigkeit.
zeitfenster_getrenntYesSind Beginn, Reinigung der Glasfläche und anschließende Pflege klar getrennt dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 safety profile is covered. The description adds the domain constraint that care water must not be counted in the suction measurement, which is genuinely useful semantics, but it says nothing about what the tool does with the four values, whether it returns a split, a verdict, or a rejection, and there is no output schema to cover that gap.

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 clauses with no filler, but the German clause is a dense nominal phrase that is hard to parse on first read, and the English tagline restates the same idea rather than adding information. Front-loading is weak because the actionable core is buried in compound nouns.

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?

With four required parameters, no output schema, and a computation-style purpose, the description should explain what result the agent gets back and how the inputs are reconciled. Instead it leaves the entire output contract and the role of zeitfenster_getrennt unstated, which is a serious gap for a tool whose whole job is a source-separated accounting.

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 each of the four parameters carries its own description, so the baseline of 3 applies. The description contributes no additional meaning about how sammelgesamt_ml, vorher_im_tank_ml, pflege_ml, and zeitfenster_getrennt are combined, nor what the boolean gates.

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 description identifies an action ("nach Quelle auftrennen") on a specific subject (measurement water from the glass surface vs. device-care step), which conveys the subject matter, but it never says what the tool actually produces — a computation, a validation, or a classification of the submitted amounts. The name's "Mulde/Einzweck" framing is opaque, and no sibling tool is named for contrast.

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?

It gives a design principle ("Keep rinse water out of the suction performance measurement") but no condition saying when an agent should call this rather than the neighboring fenstersauger measurement tools. No prerequisites, no exclusions, no mention of what makes a valid call.

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