Skip to main content
Glama

getecoback-raumklima

waschzeichen_grad_balken_ablesen

Read-only

Zahl im Waschbottich und Balken darunter als zwei Pflegegrenzen lesen, etwa 40 Grad mit zwei Strichen — Read wash temperature and mechanical treatment from one symbol.

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>",
      "zahl": "<zahl>",
      "balken": "<balken>"
    },
    "name": "waschzeichen_grad_balken_ablesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zahlYesAbgelesene Zahl im Bottich als Text. Andere Kombinationen anhand der zugehörigen Legende klären.
balkenYesLesbare Anzahl Balken unterhalb des Zeichens.
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.

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 and locality are covered. The description adds one genuinely useful behavioral fact beyond them: a single symbol encodes two distinct care limits (temperature plus mechanical treatment), which shapes how the agent should interpret the result. It says nothing about how ambiguous or unreadable cases are resolved or what the response looks like.

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?

Short and front-loaded, with the core action first and the illustrative example attached. The same content is essentially stated twice in German and English, which is mild redundancy but keeps the definition tight overall.

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 three-required-parameter, enum-driven, read-only tool with no output schema, the description covers what is read and that two limits come out. It is still thin on how 'andere'/'unlesbar' inputs are meant to resolve and on what the returned limits look like, which the absent output schema leaves unaddressed.

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 all three parameters enum-constrained and documented, so the schema carries the param burden and a 3 is the baseline. The example '40 Grad mit zwei Strichen' does add a little meaning by showing how zahl and balken pair up in practice, but it does not go beyond that.

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?

Names a concrete verb (lesen/read) and a concrete resource (the Zahl im Waschbottich plus the Balken beneath it), and states the unit of work: one symbol yields two care limits. It is bilingual and specific enough to be distinguishable, but it never names or contrasts itself with close siblings such as waschzeichen_handwaesche_umgebung_oder_40 or pflegeetikett_foto_zeichenrand_und_balken.

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, when-not-to-use, or alternative-selection sentence. The example 'etwa 40 Grad mit zwei Strichen' illustrates an input, not a decision rule, so an agent must infer from context alone when this reader rather than a sibling symbol reader applies.

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