Skip to main content
Glama

getecoback-raumklima

textil_etikett_futter_oberstoff_pflegeweg

Read-only

Bei abnehmbaren Stoffteilen den dokumentierten gemeinsamen Pflegeweg prüfen — Reconcile wash, flat-dry and air-hang instructions for detachable fabric layers.

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_gesamt_bekannt": "<etikett_gesamt_bekannt>",
      "trennbar": "<trennbar>",
      "a": "<a>",
      "b": "<b>",
      "ganzer_verbund_freigabe": "<ganzer_verbund_freigabe>"
    },
    "name": "textil_etikett_futter_oberstoff_pflegeweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesBelegter Pflegeweg für Stoffteil A.
bYesBelegter Pflegeweg für Stoffteil B.
trennbarYesDürfen die Teile laut Anleitung getrennt gepflegt werden?
etikett_gesamt_bekanntYesSind vorliegende Pflegevorgaben für das Gesamtstück und beide Stoffteile vollständig geprüft?
ganzer_verbund_freigabeYesErlaubt die Anleitung das gemeinsame Vorgehen für den gesamten Verbund grundsätzlich?

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 safety and locality are covered structurally. The description adds that the check is against a 'dokumentierten' shared care path, but says nothing about what happens when the paths disagree, whether a negative result blocks anything, or how the required completeness flags affect the outcome.

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 applicable condition front-loaded before the action. The bilingual restatement is mildly redundant but each half serves a reader, so nothing is clearly wasted.

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 read-only five-parameter reconciliation tool with no output schema, the description explains what is being compared but not the decision it produces or what an incomplete label state yields. An agent knows when to call it but not what to expect back, which is a real gap given no output schema exists.

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% with per-property descriptions and enums for a and b, so the schema carries parameter meaning. The description adds a little framing by tying the operation to a jointly documented care path, but does not explain how the two boolean gates (etikett_gesamt_bekannt, ganzer_verbund_freigabe) interact with the a/b comparison.

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?

Names a concrete action (prüfen/reconcile) on a concrete resource (the documented common care path for detachable fabric layers), which is far more specific than the opaque tool name. It stops short of differentiating itself from the many other textil_* care tools, so an agent can't cleanly route between them from the text alone.

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 opening clause 'Bei abnehmbaren Stoffteilen' gives an implicit trigger condition — use this when detachable parts are involved. There is no explicit when-not, no prerequisite about label completeness, and no named alternative among the sibling care tools.

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