Skip to main content
Glama

getecoback-raumklima

spuelmaschine_beladung_vergleichen

Read-only

Für dieselbe Anzahl Maßgedecke passende Beladungen und deren Strom- und Wasserbedarf prüfen. — Compare different dishwasher load sizes for the same number of clean place settings.

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": {
      "gesamt_gedecke": "<gesamt_gedecke>",
      "gedecke_a": "<gedecke_a>",
      "gedecke_b": "<gedecke_b>",
      "kwh_a": "<kwh_a>",
      "kwh_b": "<kwh_b>",
      "liter_a": "<liter_a>",
      "liter_b": "<liter_b>"
    },
    "name": "spuelmaschine_beladung_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwh_aYesGemessene kWh je Lauf in Variante A.
kwh_bYesGemessene kWh je Lauf in Variante B.
liter_aYesGemessene Liter je Lauf in Variante A.
liter_bYesGemessene Liter je Lauf in Variante B.
gedecke_aYesGedecke je Lauf in Variante A.
gedecke_bYesGedecke je Lauf in Variante B.
gesamt_gedeckeYesAnzahl gleicher zu reinigender Maßgedecke.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 comparison dimensions, but it does not describe the return behavior, result format, or any additional constraints beyond read-only comparison.

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?

The description is one front-loaded bilingual sentence with no filler. The German and English versions are redundant, but the duplication is brief and does not obscure the purpose.

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 read-only tool with seven required parameters and a fully described schema, the description covers the core comparison purpose adequately. However, with no output schema present, it leaves open what the comparison result contains and does not clarify how the A/B loads are evaluated.

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 schema already documents all seven parameters, including the A/B variants and units. The description mentions same-number place settings and energy/water demand at a high level, but adds no syntax, range, or variant meaning 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?

States a specific verb (prüfen/compare), resource (Beladungen/load sizes), and comparison criteria: same number of Maßgedecke plus Strom- und Wasserbedarf. It does not explicitly name or distinguish itself from sibling dishwasher tools, so it falls short of full sibling differentiation.

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 by 'für dieselbe Anzahl Maßgedecke' and the comparison of two variants, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer the scenario but is not routed away from close siblings.

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