Skip to main content
Glama

getecoback-climate-weather

spuelmaschine_zubehoer_korb_umbauwechsel

Read-only

Zwei tatsächlich getestete Korbpositionen für hohe Gläser und hohe Teile auf einen unveränderlichen Lauf prüfen. — Compare feasible baskets layouts when one run must hold both tall glasses and tall pieces.

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": {
      "glaeser": "<glaeser>",
      "grosse_teile": "<grosse_teile>",
      "glaeser_stellung_a": "<glaeser_stellung_a>",
      "teile_stellung_a": "<teile_stellung_a>",
      "glaeser_stellung_b": "<glaeser_stellung_b>",
      "teile_stellung_b": "<teile_stellung_b>"
    },
    "name": "spuelmaschine_zubehoer_korb_umbauwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
glaeserYesBenötigte Zahl der gleich hohen Gläser.
grosse_teileYesBenötigte Zahl der hohen Teile im anderen Korb.
teile_stellung_aYesGemeinsam nutzbare Plätze für die hohen Teile bei Stellung A.
teile_stellung_bYesGemeinsam nutzbare Plätze für die hohen Teile bei Stellung B.
glaeser_stellung_aYesGemeinsam nutzbare hohe Glasplätze bei Stellung A.
glaeser_stellung_bYesGemeinsam nutzbare hohe Glasplätze bei Stellung B.

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 useful provenance ('tatsächlich getestete Korbpositionen') and the single-run constraint, but says nothing about what the check returns (per-position feasibility, counts, failures), which is the main behavioral question for a comparison tool.

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 sentences, with the operative constraint front-loaded and the English version serving as gloss. The German/English duplication is slight padding but does not obscure the core intent.

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 six-parameter read-only comparison with no output schema, the definition covers the scenario but not the result shape an agent would need to interpret (what a feasible versus infeasible layout looks like). Adequate but with a clear gap given the absence of an output schema.

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%, with every one of the six required parameters carrying its own German description, so the schema does the heavy lifting. The description adds only the framing that A and B are competing positions under one run, not any clarification of units, ranges, or how demand versus shared slots combine.

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 concrete operation (prüfen/compare two tested basket positions A and B for tall glasses and tall parts) and a concrete constraint (a single unchangeable run). It tells an agent this is a feasibility comparison rather than a generic load comparison, though the bilingual restatement does more work than the tool name does.

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 clause 'when one run must hold both tall glasses and tall pieces' gives the triggering condition, but there is no explicit when-not guidance and no sibling such as spuelmaschine_beladung_vergleichen is named as the alternative. Usage must be inferred from the scenario sentence.

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