Skip to main content
Glama

getecoback-raumklima

bleichzeichen_dreieck_markierung_ablesen

Read-only

Leeres, gestreiftes oder durchgestrichenes Dreieck auf dem Pflegeetikett lesen — Decode all bleaching, oxygen-only bleaching or no bleaching.

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>",
      "dreieck": "<dreieck>"
    },
    "name": "bleichzeichen_dreieck_markierung_ablesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
dreieckYesZeichen vollständig abgelesen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the safety profile is covered. The description adds the useful domain detail that the output meaning spans bleaching / oxygen-only bleaching / no bleaching, but says nothing about how ambiguous cases ('unklar' is an allowed input) are handled 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?

Two compact clauses with the symbol states front-loaded and no filler; the bilingual phrasing is slightly redundant but does not obscure the meaning. Every element earns its place.

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

Completeness4/5

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

For a 2-parameter, fully-schema-documented, read-only decoding tool with no output schema, the description gives enough to call it correctly and indicates the range of possible conclusions. A note on how ambiguous readings should be recorded would close the remaining gap.

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 parameters carry enum values with their own descriptions, so the schema does the work. The description adds no extra meaning about 'quelle' provenance handling or the difference between 'zwei_schraegstriche' and 'durchgestrichen', leaving it at the baseline.

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?

States a concrete verb+resource: reading the empty, striped, or crossed-out triangle on a care label, and names the three symbol states it decodes. This is clearly distinguishable from a washing-symbol reader by the explicit 'bleaching' framing, though it never names a sibling to contrast against.

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: an agent can infer it should call this when a bleaching triangle needs interpreting. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as other label-marking readers, so the agent must infer boundaries from the resource name 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