Skip to main content
Glama

getecoback-climate-weather

bleichzeichen_gegen_waschmittel_herstellerdeklaration

Read-only

Ein am Stoff eindeutig gelesenes Bleichdreieck gegen die Herstellerdeklaration des Wasch- oder Fleckenmittels abgleichen — Check the declared bleaching class against a garment restriction.

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": {
      "etikett": "<etikett>",
      "deklaration": "<deklaration>"
    },
    "name": "bleichzeichen_gegen_waschmittel_herstellerdeklaration"
  }
}

Input Schema

NameRequiredDescriptionDefault
etikettYesBereits sicher interpretiertes Dreieck am konkreten Stück.
deklarationYesExplizite Deklaration des konkreten Mittels. Marketingwörter allein als „kein_klassenbeleg“ erfassen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 that this is a reconciliation of two already-established facts rather than a lookup or a write, but it does not disclose what the comparison produces (a verdict, a conflict flag, a warning) — a meaningful gap for a tool whose whole purpose is the outcome of a check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the input, the reference point, and the operation with zero filler. The German/English doubling is a deliberate bilingual convention rather than padding, and nothing needs to be skimmed past to find the purpose.

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 two-enum comparison tool with full schema coverage and read-only annotations, the definition supplies everything needed to invoke it correctly. The one omission is what the return looks like (no output schema exists and the description does not hint at the result shape), but the invocation itself is unambiguous.

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 are closed enums with self-explanatory values, so the schema carries the semantic load. The description's phrase 'eindeutig gelesen' reinforces the etikett constraint but adds no syntax, format, or interpretation detail beyond what the enum descriptions already state.

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

Purpose5/5

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

The description names a specific verb (abgleichen) and both resources (Bleichdreieck vs. Herstellerdeklaration des Wasch-/Fleckenmittels). The qualifier 'am Stoff eindeutig gelesen' distinguishes it from the sibling that reads the marking (bleichzeichen_dreieck_markierung_ablesen): this tool consumes an already-interpreted symbol and performs the compatibility check.

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?

The prerequisite that the triangle must already be clearly read is stated, which implies when this tool applies. However, there is no explicit when-not guidance, no named alternative for the case where the symbol is not yet read, and no statement about what to do when the declaration lacks a class beyond the enum value 'kein_klassenbeleg'.

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