Skip to main content
Glama

getecoback-raumklima

spuelgang_sichtbare_reste_schwerpunkt

Read-only

Nach gleicher Beladung sichtbare Nacharbeit nach Korb und Zugänglichkeit einordnen. — Find where visible rework concentrates after equal dishwasher loads.

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": {
      "teile_oben": "<teile_oben>",
      "teile_unten": "<teile_unten>",
      "sichtreste_oben": "<sichtreste_oben>",
      "sichtreste_unten": "<sichtreste_unten>"
    },
    "name": "spuelgang_sichtbare_reste_schwerpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
teile_obenYesKontrollierte Teile im oberen Korb.
teile_untenYesKontrollierte Teile im unteren Korb.
sichtreste_obenYesOben kontrollierte Teile mit sichtbaren Resten.
sichtreste_untenYesUnten kontrollierte Teile mit sichtbaren Resten.

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 safety is covered and the description does not need to restate it. The description adds the equal-load comparability constraint, but says nothing about how the result is expressed (rates, ranking, per-basket share), and there is no output schema to fall back on.

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, front-loaded with the operative constraint, with no filler. The German/English duplication is mildly redundant but serves as a quick gloss rather than padding.

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 four-required-number computation with no output schema, the definition leaves the shape of the result undefined, which is the main gap an agent would want closed. Inputs and preconditions are adequately covered.

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% and each of the four counts is documented in German, so the parameters are already self-explanatory. The description adds the implicit constraint that oben/unten counts must stem from the same load, but contributes no further meaning about the relationships between the four numbers.

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 analytical task: classifying visible rework by basket (Korb) and accessibility after equal loads, which is concrete enough to distinguish it from siblings like spuelgang_nachwaschaufwand. 'Einordnen' is somewhat abstract, but the English gloss 'Find where visible rework concentrates' pins down the intent.

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?

'Nach gleicher Beladung' supplies a real precondition (only meaningful when loads were comparable), which is useful guidance. However, it offers no explicit when-not conditions and does not point to any alternative tool for related cleaning diagnostics.

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