Skip to main content
Glama

getecoback-climate-weather

saugwischer_zwei_haushaltsteam_verschleissteilsatz

Read-only

Zwei getrennte geplante Reinigungen mit bestätigten vollständigen Teilesätzen abgleichen — Detect which cleaning team can start with the model-approved parts on hand.

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": {
      "eins_komplett": "<eins_komplett>",
      "zwei_komplett": "<zwei_komplett>",
      "zusatz_passt_eins": "<zusatz_passt_eins>",
      "zusatz_passt_zwei": "<zusatz_passt_zwei>",
      "eins_fest_vorrang": "<eins_fest_vorrang>"
    },
    "name": "saugwischer_zwei_haushaltsteam_verschleissteilsatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
eins_komplettYesTeam 1 hat einen vollständigen trockenen, passenden Teilesatz.
zwei_komplettYesTeam 2 hat ebenfalls einen getrennten vollständigen passenden Satz.
eins_fest_vorrangYesVorherige Vereinbarung gibt Team 1 bei konkurrierender Nachfrage Vorrang.
zusatz_passt_einsYesEin zusätzlich verfügbarer Satz ist für Team 1 und dessen Modell bestätigt.
zusatz_passt_zweiYesDerselbe zusätzliche Satz ist für Team 2 und dessen Modell bestätigt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, which matches a pure boolean computation, so there is no contradiction and the safety bar is low. The description adds that the check hinges on 'model-approved' complete sets, which is useful context. However, it omits the decision behavior that matters most: what happens when both teams are complete, and how eins_fest_vorrang breaks the tie.

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 a single sentence, which is efficient, but it is a German clause followed by an English clause that neither translates nor extends the first — the two halves partly duplicate and partly diverge ('model-approved parts on hand' vs. 'bestätigten vollständigen Teilesätzen'). The lack of a stated outcome means the sentence is short without being front-loaded on what the caller needs.

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?

With five required booleans, no output schema, and only minimal annotations, the description would need to explain the returned decision and the precedence rule. It does not: the meaning of the vote when both teams are complete, and whether eins_fest_vorrang ever overrides an incomplete team, are left entirely to inference. For a decision-arbitration tool this is a substantial 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%, so every one of the five boolean parameters is already documented in the schema, and the description adds no further semantics beyond them. Per the high-coverage baseline this sits at 3. The description's phrase 'model-approved parts on hand' loosely echoes zusatz_passt_* and eins_komplett but explains no new meaning.

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 does name an operation ("abgleichen" / "Detect which cleaning team can start") on a specific resource (two planned cleanings with confirmed complete part sets), so the intent is roughly graspable. But the opaque German compound name and missing title mean the description alone must carry the meaning, and it never says what the tool actually produces (a team decision, a boolean, a ranked answer). An agent knows the domain but not the concrete outcome.

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 when-to-use guidance, no when-not-to-use, and no reference to any alternative despite many sibling tools covering adjacent cleaning-planning decisions (e.g. saugwischer_reihenfolge_trockener_ausgang, saugwischer_uebergabe_bodenabschnitt_freigaben). Nothing tells the agent under which circumstances this arbitration tool should be selected over those.

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