Skip to main content
Glama

getecoback-raumklima

textilfaserangabe_und_pflegekennzeichnung_trennen

Read-only

Baumwoll-, Woll- oder Mischgewebeangabe von einer eigenständigen Pflegekennzeichnung unterscheiden — Track the separate evidence for fibre composition and garment care.

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": {
      "faserangabe": "<faserangabe>",
      "pflegeangabe": "<pflegeangabe>"
    },
    "name": "textilfaserangabe_und_pflegekennzeichnung_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
faserangabeYesSteht eine eindeutige Faserzusammensetzung auf dem Textil oder in der zugeordneten Kennzeichnung?
pflegeangabeYesLiegt für die gesuchte Behandlung eine eindeutige Pflegeangabe dieses konkreten Stücks vor?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 safety is covered, but the description adds almost nothing beyond that: it does not say how the two booleans combine, what happens when both are true or both false, or what evidence the caller receives back. The phrase 'Track the separate evidence' hints at a classification/recording behavior without explaining it.

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 with the key distinction stated first, followed by a short English gloss. The bilingual duplication is mildly redundant but adds nuance rather than noise.

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-boolean read-only classifier the definition is serviceable, and the schema fully documents inputs, but with no output schema the caller still has no idea what the result looks like or how to interpret a true/true combination. One more sentence on the return shape would close the 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 booleans carry precise German descriptions about whether a clear fibre composition or a per-garment care instruction is present. The description adds no further meaning about how these two flags interact or what combinations are valid, so the baseline of 3 applies.

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

Purpose3/5

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

The description names the two resources being disambiguated (fibre composition vs. a standalone care label), so the domain is identifiable, but it never states what the tool actually returns or decides — 'Track the separate evidence' is vague about the operation's output. Among the many '*_trennen' siblings, the textile domain distinguishes it, yet no explicit contrast with an alternative is given.

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 statement of when to call this tool, when not to, or what alternative to use if the labels are not separate. The agent must infer the trigger condition entirely from the tool name and the boolean parameters.

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