Skip to main content
Glama

getecoback-climate-weather

spueler_geschirr_material_vor_einraeumen_beleg

Read-only

Vor dem Einräumen Werkstoff und explizite Geschirrfreigabe beim exakten Modell prüfen — Screen documented dishware and material limitations before loading.

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": {
      "modell": "<modell>",
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "material": "<material>",
      "geschirrhersteller": "<geschirrhersteller>"
    },
    "name": "spueler_geschirr_material_vor_einraeumen_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaues Modell aus den deutschen Unterlagen.
materialYesDokumentierter Werkstoff oder Gegenstand.
geschirrherstellerYesOriginalangabe für genau dieses Geschirrteil.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

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 bar is lower. The description usefully adds that only documented evidence counts, but it never says what the call returns (a suitability verdict, a refusal, an evidence record) despite there being no output schema, which is the main behavioral gap.

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?

A single compact sentence with the action and its timing front-loaded, so the agent hits the operative instruction immediately. The German and English renderings are duplicates rather than additive content, which is the only real waste.

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?

With four required parameters, three of them enumerated, and a documented-evidence model, an agent needs to know what comes back and how a negative evidence case is signalled; the description is silent on both. It is adequate to know when to call, but incomplete for interpreting the result of a decision-style tool.

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 coverage is 100% with enum values and per-property descriptions for all four required parameters, so the schema does the heavy lifting. The description reinforces 'exaktes Modell' and 'expletite Geschirrfreigabe', which maps loosely to the modell and geschirrhersteller enums, but adds no new semantics such as acceptable values or what 'kein_passender_beleg' triggers.

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 verb (prüfen/screen) and a specific resource pair (Werkstoff und explizite Geschirrfreigabe beim exakten Modell), scoped to the moment before loading. An agent can tell it is a documentation-based suitability check rather than a physical action. It does not name any sibling to distinguish itself from, keeping it short of a 5.

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 only implied through the temporal qualifier 'Vor dem Einräumen', which tells the agent when in the workflow to call it. There is no explicit statement of when not to use it, no alternative tool named, and no prerequisite about having the German documentation on hand.

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