Skip to main content
Glama

getecoback-climate-weather

saugwischer_pad_reserve_mit_ruecklauf

Read-only

Freigegebene Wischpads mit geprüften Rückläufen auf drei getrennte Einsätze verteilen — Check clean-pad availability across three appointments and their return times.

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": {
      "freigegeben": "<freigegeben>",
      "anfang": "<anfang>",
      "je_einsatz": "<je_einsatz>",
      "ruecklauf_vor_zwei": "<ruecklauf_vor_zwei>",
      "ruecklauf_vor_drei": "<ruecklauf_vor_drei>"
    },
    "name": "saugwischer_pad_reserve_mit_ruecklauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
anfangYesZu Beginn saubere, verwendbare Pads.
je_einsatzYesFür jeden der drei Einsätze erforderliche frische Pads.
freigegebenYesSind der Padtyp und die Pflege nach Gebrauch für das konkrete Modell bestätigt?
ruecklauf_vor_dreiYesVor Einsatz 3 zusätzlich als bereit geprüfte Pads.
ruecklauf_vor_zweiYesVor Einsatz 2 zusätzlich als bereit geprüfte Pads.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful constraint that pads must be 'freigegeben/geprüft' before counting and that returns only land at fixed points before appointments 2 and 3. However, it never says what the call produces (a feasibility verdict, an allocation, a shortfall count) — notable for a tool with no output schema — and the word 'verteilen' faintly suggests a mutation that the readOnly annotation denies; the English 'Check' clause resolves this, so it is not a true contradiction.

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 short clauses with the operation and scope front-loaded; nothing extraneous. The German and English halves largely restate each other, which aids comprehension but is mild duplication rather than new information.

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?

All five parameters are required and fully documented in the schema, and annotations cover safety, so the basics are present. What is missing is the outcome: with no output schema, the description should state what an agent gets back from a pad-reserve check. The gate condition (freigegeben) is also not described as a precondition with consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains each field, making 3 the baseline. The description nonetheless adds framing the schema does not: that there are exactly three Einsätze and that the ruecklauf_* values are checked against appointments 2 and 3 specifically, which tells the agent how the five params combine. It does not explain the semantics of 'je_einsatz' being a single value applied to all three.

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 resource (freigegebene Wischpads with verified returns) and scope (three separate Einsätze), plus an English gloss that frames it as a clean-pad availability check. An agent can tell roughly what domain this computes, though the pairing of 'verteilen' (distribute) and 'check availability' leaves the actual operation slightly ambiguous. No sibling is named or contrasted.

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 scenario is implied — use it when you need to verify pad availability across three appointments accounting for return times before appointments 2 and 3. There is no explicit when-not guidance and no routing to related siblings such as saugwischer_gebraucht_startmaterial_budget or saugwischer_freigegebene_abschnitte_flaechenbilanz, even though the sibling list shows many adjacent pad/budget 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