Skip to main content
Glama

getecoback-raumklima

geschirrkorb_ausraeumfolge_tropfen_unten

Read-only

Zwei Ausräumfolgen auf neu benetzte Teile im unteren Korb prüfen — Compare lower-rack drips after two observed unloading orders.

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_unten": "<teile_unten>",
      "neu_nass_a": "<neu_nass_a>",
      "neu_nass_b": "<neu_nass_b>",
      "gleichartige_proben": "<gleichartige_proben>"
    },
    "name": "geschirrkorb_ausraeumfolge_tropfen_unten"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_nass_aYesTeile, die beim Ausräumen in Folge A zusätzlich Tropfen bekamen.
neu_nass_bYesEntsprechende Teile in Folge B.
teile_untenYesJe Probe gleich viele unten kontrollierte Teile.
gleichartige_probenYesSind Anordnung, voriger Spülgang und Beobachtung bis zum Ausräumen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 profile is covered. The description adds domain context about lower-rack drips and two observed unloading orders, but does not explain comparison behavior, handling of non-comparable samples, or result interpretation.

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 definition is a single, front-loaded sentence with a bilingual restatement. It is efficient and easy to scan, though the English duplicate adds length without much new information.

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-parameter comparison tool with full schema coverage and read-only annotations, the description is adequate for invocation. However, it does not clarify what the comparison produces or how non-comparable samples are treated, leaving a gap against 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%, so all four parameters are already well documented in the schema. The description reinforces that the comparison concerns lower-rack newly wetted parts across sequences A and B, but adds little semantic detail 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?

The description states a specific action — comparing two unloading sequences for newly wetted parts in the lower basket — and names the observable object (drips after unloading). It is clear what the tool does, though it does not explicitly distinguish itself from any sibling.

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 implies the tool is used after two observed unloading orders, but gives no explicit when-to-use, when-not-to-use, or alternative tool guidance. The agent must infer the applicable situation from the purpose statement alone.

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