Skip to main content
Glama

getecoback-climate-weather

spueler_vorbereitung_grobe_reste_auto_sensor

Read-only

Geschirrvorbereitung und maschineneigenes Vorspülen vor einem Automatikvergleich trennen — Separate scraping, rinsing under the tap and the machine’s internal prewash.

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": {
      "vorbereitung": "<vorbereitung>",
      "auto_sensor_belegt": "<auto_sensor_belegt>",
      "maschinen_vorspuelphase": "<maschinen_vorspuelphase>"
    },
    "name": "spueler_vorbereitung_grobe_reste_auto_sensor"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorbereitungYesWelche Vorbereitung an dieser Ladung ist beobachtet?
auto_sensor_belegtYesLief nachweislich das dokumentierte sensorabhängige Automatikprogramm?
maschinen_vorspuelphaseYesWas steht in der Tabelle für diesen internen Schritt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint and openWorldHint annotations already establish a safe, closed-world read operation, and the description adds the useful domain context that preparation steps are separated from machine prewash. It does not explain what the invocation returns or how the observations are handled after submission.

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 compact sentence with the key distinction front-loaded and an English translation. The bilingual restatement is slightly redundant but not wasteful.

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

Completeness2/5

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

For a tool with three required parameters and no output schema, the description leaves important completeness gaps: it does not say what the tool produces, whether it stores an observation, or how the automatic comparison consumes the inputs. The annotations and complete schema help, but the description does not fully cover the operational contract.

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 three parameters are already documented in the schema. The description broadly maps to scraping, tap rinsing, and machine prewash, but adds little parameter-specific meaning beyond that conceptual separation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific domain distinction: dish preparation, manual rinsing, and the machine's internal prewash before an automatic comparison. However, it does not clearly state whether the tool records, classifies, validates, or compares these observations, so the purpose is only partly clear.

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 before an automatic comparison, but gives no explicit when-to-use guidance, prerequisites, or alternatives among the many sibling tools. The agent must infer the invocation context.

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