Skip to main content
Glama

getecoback-raumklima

spuelgang_nachwaschaufwand

Read-only

Gemessenen Wasser- und Stromaufwand zusätzlicher Spülgänge pro gewünschter fertiger Ladung aufschlüsseln — Account for actual repeat cycles when assessing dishwasher results.

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": {
      "ladungen": "<ladungen>",
      "nachgaenge": "<nachgaenge>",
      "nachgang_l": "<nachgang_l>",
      "nachgang_kwh": "<nachgang_kwh>"
    },
    "name": "spuelgang_nachwaschaufwand"
  }
}

Input Schema

NameRequiredDescriptionDefault
ladungenYesGewünschte fertig gespülte Ladungen im Protokoll.
nachgaengeYesZusätzlich nötige vollständige Maschinengänge im Protokoll.
nachgang_lYesLiter pro beobachtetem Nachgang.
nachgang_kwhYeskWh pro beobachtetem Nachgang.

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 establish readOnlyHint=true and openWorldHint=false, so safety is covered and the description need not repeat it. The description adds that this is an attribution/accounting operation based on measured values, which tells the agent it is a derived-metric computation rather than a data fetch. It does not say what the returned breakdown contains (per-load liters vs kWh, rounding, whether totals are also returned), and there is no output schema to cover that.

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?

Two compact clauses with the core operation front-loaded in the German sentence. The English tail is not a pure translation (it adds the 'when assessing results' framing), so it earns most of its place, though the bilingual duplication is slightly redundant for a tool this small.

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

Completeness4/5

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

Four required numeric parameters, no nested objects, no output schema, and full schema descriptions mean the description only needs to frame intent, which it does. The main residual gap is that the output quantity's form (per-load water and energy figures) is only implied, which matters because the whole point of the tool is the normalized result.

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 the four parameters (ladungen, nachgaenge, nachgang_l, nachgang_kwh) are already fully documented in the schema and the baseline of 3 applies. The description only alludes to two of them at a high level (water and energy per repeat cycle) and adds no format, unit-convention or edge-case meaning beyond what the schema provides.

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 German clause names a concrete operation ('aufschlüsseln' = break down/allocate) over concrete resources (Wasser- und Stromaufwand zusätzlicher Spülgänge) and states the normalization basis ('pro gewünschter fertiger Ladung'). That is a real verb+resource+scope, not a restatement of the tool name. It stops short of 5 because the normalization denominator is stated only in prose and the tool's relation to any sibling is left implicit.

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?

The trailing English sentence ('Account for actual repeat cycles when assessing dishwasher results') implies the situation in which this tool applies, namely attributing real re-wash cycles rather than nominal ones. It gives no when-not condition and names no alternative tool for the plain per-cycle or per-load case. Usage is therefore suggested but not routed.

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