Skip to main content
Glama

getecoback-raumklima

textil_zwei_pflegeintervalle_abgleich

Read-only

Zwei ausdrücklich dokumentierte Pflegeschritte samt gemeinsamer Gelegenheit in einem Kalender prüfen — Check whether two recurring textile care steps can share a documented window.

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": {
      "feste_intervalle": "<feste_intervalle>",
      "erster_resttag": "<erster_resttag>",
      "intervall_a": "<intervall_a>",
      "zweiter_resttag": "<zweiter_resttag>",
      "intervall_b": "<intervall_b>",
      "horizont": "<horizont>"
    },
    "name": "textil_zwei_pflegeintervalle_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
horizontYesAnzahl Tage bis zum einschließenden Ende des Planungsfensters.
intervall_aYesTage zwischen den Terminen für A.
intervall_bYesTage zwischen den Terminen für B.
erster_resttagYesTage bis zum nächsten geplanten Termin für Pflege A.
zweiter_resttagYesTage bis zum nächsten geplanten Termin für Pflege B.
feste_intervalleYesSind beide Intervalle belegt und ist die gemeinsame Durchführung freigegeben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish this as a safe, closed-world read-only computation, so the bar is lower. The description adds context beyond that — both care steps must be explicitly documented and the check targets a shared calendar opportunity — but it says nothing about what the check returns or how ties/near-misses are treated.

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?

It is short, but the German sentence is convoluted ('samt gemeinsamer Gelegenheit in einem Kalender') and the English clause simply restates it, so the bilingual duplication spends words without adding information. Nothing is wasted on filler, but the phrasing is not front-loaded or crisp.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter computation with no output schema, the description should at least indicate the shape of the result (boolean overlap vs. concrete dates/window) and the meaning of a 'documented window'. It does neither, leaving an agent able to invoke it but unable to predict or interpret its output.

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 six parameters (intervall_a/b, erster/zweiter_resttag, horizont, feste_intervalle) are already documented in the schema. The description adds no extra meaning about units, inclusive ends, or the horizon cap beyond what the schema states, 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 names a specific verb ('prüfen' / 'Check') and a specific resource ('zwei Pflegeschritte' / 'two recurring textile care steps') plus the decision being made: whether both can share one documented window. That is enough to distinguish it from siblings like textil_pflege_nutzungszyklen_protokoll, though it never explicitly contrasts itself with any of them.

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 an implicit precondition in 'ausdrücklich dokumentierte Pflegeschritte' (both steps must already be documented), but no explicit statement of when to call this versus the many other 'abgleich' siblings, and no when-not-to-use guidance or mention of alternatives.

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