Skip to main content
Glama

getecoback-raumklima

thermovorhang_pflegeetikett_verfahren

Read-only

Vergleiche die gewünschte Reinigungsart mit dem Pflegeetikett des Vorhangs — Match curtain cleaning needs to the care 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": {
      "benoetigte_pflege": "<benoetigte_pflege>",
      "etikett": "<etikett>",
      "temperatur_c": "<temperatur_c>",
      "maximum_c": "<maximum_c>"
    },
    "name": "thermovorhang_pflegeetikett_verfahren"
  }
}

Input Schema

NameRequiredDescriptionDefault
etikettYesKlar lesbare Waschfreigabe
maximum_cYesVermerkte Höchsttemperatur in °C, 0 ohne Angabe
temperatur_cYesGeplante Waschtemperatur in °C
benoetigte_pflegeYesReinigungsart, die zu Hause möglich und gewünscht ist

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It confirms the tool is a pure comparison rather than an action, but says nothing about the verdict produced or how ambiguous inputs (etikett="offen", maximum_c=0) are handled.

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 short sentence with the key terms front-loaded and zero filler; the bilingual gloss is slightly redundant but aids matching. Nothing is buried or padded.

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, closed-world comparison with no output schema, the definition should at least sketch the shape of the result (a verdict, a recommendation, a conflict flag). It establishes the inputs' relationship but leaves the return value entirely unspecified.

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 all four parameters are already documented in the schema, including the enums and the 0-means-unspecified convention for maximum_c. The description adds no parameter-level meaning beyond restating which two values are compared, so the baseline 3 applies.

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 states a concrete verb ("Vergleiche") against two concrete resources (gewünschte Reinigungsart vs. Pflegeetikett des Vorhangs), so the operation is unambiguous. It does not, however, distinguish itself from the closely-named sibling waesche_pflegetikett_programmabgleich, leaving the agent to infer the boundary from names 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?

Usage is only implied by the comparison itself: an agent can guess this is the check to run before choosing a cleaning method for a thermal curtain. There is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative.

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