Skip to main content
Glama

getecoback-raumklima

pflegeetikett_fehlendes_eingenaehtes_etikett_suchweg

Read-only

Bei einem fehlenden Pflegeetikett zuerst den empfohlenen Anbringungsort und dann stückbezogene Ersatzdokumentation prüfen — Find a care authority when a garment appears to have no sewn-in label.

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": {
      "anbringung": "<anbringung>",
      "unterlage": "<unterlage>"
    },
    "name": "pflegeetikett_fehlendes_eingenaehtes_etikett_suchweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
unterlageYesAlternative Herstellerunterlage zum konkreten Stück.
anbringungYesErgebnis der Sicht am für die Artikelart empfohlenen Ort.

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?

The annotations already establish that this is a non-mutating, closed-world read operation. The description adds the diagnostic ordering of the two checks, but it does not explain what the tool returns, how the enum combinations alter the guidance, or what happens after the checks are recorded. With no output schema, that behavioral gap matters.

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

Conciseness3/5

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

The definition is short, but the German and English portions are partly redundant rather than complementary, and the em-dash structure makes the relation between them less crisp. The triggering condition is front-loaded, though the English tagline weakens the otherwise clear procedural statement.

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-parameter triage/search-path tool with no output schema, the description explains the initial checks but does not say what the tool produces or how to act on specific combinations of 'anbringung' and 'unterlage'. The core calling context is present, but the post-check behavior remains underspecified.

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%, so both enum parameters are already documented in the input schema. The description conceptually frames the two checks (attachment location and item-specific replacement documentation), but it adds no further meaning about the enum values or how they should be interpreted together.

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 identifies a specific scenario (a garment that appears to have no sewn-in care label) and a clear diagnostic sequence: check the recommended attachment location first, then item-specific replacement documentation. The phrase 'Find a care authority' is somewhat vague and the mixed German/English wording slightly muddies the core action, but the tool is distinguishable from the many more specific care-label siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance for missing sewn-in labels and even specifies the order of checks to perform. It does not name when not to use this tool or point to alternative sibling tools, but the triggering condition is clear.

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