Skip to main content
Glama

getecoback-climate-weather

waschzeichen_handwaesche_umgebung_oder_40

Read-only

Handwäsche bis 40 Grad, schonende Handwäsche bei Umgebungstemperatur und durchgestrichenen Waschbottich auseinanderhalten — Distinguish both hand-wash symbols and no household washing.

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": {
      "quelle": "<quelle>",
      "zeichen": "<zeichen>"
    },
    "name": "waschzeichen_handwaesche_umgebung_oder_40"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
zeichenYesVariante aus der passenden Legende. Bei einem unscharfen Handzeichen „nicht_eindeutig“ wählen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 essentially no behavioral context beyond the subject matter: it does not say that the result is a classification decision, how ambiguity is handled, or what the caller should supply as evidence. With annotations carrying the safety burden, this is a modest but real 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?

One front-loaded sentence with the scope stated first; nothing is buried. The bilingual tail is partly redundant ('Handwäsche bis 40 Grad' restated as 'both hand-wash symbols'), but it is short enough that the cost is minimal and it aids non-German readers.

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 two-parameter, fully enumerated classification tool this is close to sufficient, and the schema covers all inputs. However, with no output schema, the description never tells the agent what comes back (a chosen symbol label, a verdict, or explanatory text), which is a noticeable gap for a decision tool. The mixed German/English phrasing also leaves the exact deliverable implicit.

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 both enum parameters (quelle, zeichen) are fully documented in the schema, including the instruction to choose 'nicht_eindeutig' for a blurry hand symbol. The description's mention of the three zeichen variants loosely mirrors the enum but adds no new semantics about how quelle influences the answer. Baseline 3 applies when the schema does the heavy lifting.

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 the specific task (auseinanderhalten / distinguish) and enumerates the three symbol variants: hand wash up to 40 degrees, gentle hand wash at ambient temperature, and the crossed-out wash tub. That is a clear verb-plus-resource statement that an agent can match to a user's laundry-symbol question. It does not differentiate against any named alternative, though no sibling in the catalog covers the same laundry-symbol domain.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The only implicit guidance is the list of symbols in scope. An agent must infer from the tool name and enum values alone that this tool is for reading and classifying hand-wash symbols rather than, say, temperature-bar symbols.

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