Skip to main content
Glama

getecoback-climate-weather

fachpflegezeichen_kreis_p_f_w_unterscheiden

Read-only

P, F, W sowie ein Verbot von Trocken- oder Nassreinigung als Angaben für den Textilreinigungsbetrieb unterscheiden — Identify dry and wet professional care from the garment circle.

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": "fachpflegezeichen_kreis_p_f_w_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesWo wurde das konkrete Zeichen gelesen? Eine Zuordnung zum Stück separat prüfen.
zeichenYesLesbares Zeichen aus der zugehörigen Legende. Ein gefüllter durchgestrichener Kreis ist das Nassreinigungsverbot.

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 the agent knows this is a safe closed-world read/classification with no side effects. The description adds the scoping detail that only circle-based symbols (not circle-in-square tumble-dry marks) are handled, which is genuine extra context. It says nothing about how ambiguous or unreadable cases resolve in the response.

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 front-loaded sentence that leads with the symbols being discriminated, followed by a bilingual rendering of the same idea. Efficient with no filler; the German/English duplication costs a little space but aids recall across languages.

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-enum classification tool with full schema coverage and read-only annotations, this is adequate, and no output schema means return values need not be described. The gap is that the description never says what 'unterscheiden' produces for the caller or how the 'unlesbar'/'unbekannt' paths should be handled at the call level.

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% and both parameters carry their own enum descriptions, including the note that a filled struck-through circle is the wet-cleaning prohibition. The description only echoes the P/F/W values already enumerated in the schema and adds no meaning for 'quelle' (where the mark was read). Baseline 3 is appropriate 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 resource (the professional-care circle symbol on a garment) and the specific discrimination task: distinguishing P, F, W and the struck-through dry/wet cleaning prohibition. An agent can tell this is about reading a care-label circle rather than measuring or documenting something. It stops short of naming a sibling such as trocknerzeichen_kreis_im_quadrat_punkte, so the separation from look-alike symbols is only implicit.

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 implied by 'from the garment circle' and by the input field 'zeichen', which scopes the call to a symbol already read off a label. There is no explicit when-to-use/when-not and no mention of an alternative tool for related symbols, so an agent must infer the routing itself.

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