Skip to main content
Glama

getecoback-raumklima

poolreinigung_neuer_schmutzeintrag_nach_lauf

Read-only

Nach einem Poollauf beobachtete Neueinträge zeitlich von verbliebenem Schmutz trennen — Separate visible residual debris from later arrivals within marked areas.

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": {
      "laufende": "<laufende>",
      "kontrollzeit": "<kontrollzeit>",
      "neuer_eintrag": "<neuer_eintrag>",
      "unveraenderter_zeitbezug": "<unveraenderter_zeitbezug>"
    },
    "name": "poolreinigung_neuer_schmutzeintrag_nach_lauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
laufendeYesZeit des beobachteten Laufendes.
kontrollzeitYesZeit der ersten vollständigen Sichtkontrolle danach.
neuer_eintragYesProtokollierter Start des ersten später beobachteten Eintrags.
unveraenderter_zeitbezugYesGleicher Tag, durchgehender Zeitbezug und abgesicherte Quellenbeobachtung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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. Beyond that, the description adds almost nothing: it does not disclose what the four inputs are compared against, what the result looks like, or what happens when 'unveraenderter_zeitbezug' is false. With no output schema, that missing return-value disclosure is a substantive gap.

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 sentences with the core operation stated first and no filler. The bilingual structure is redundant in places — the English version is a close paraphrase rather than complementary information — but nothing is buried or padded.

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 four-required-parameter computation tool with no output schema, the description should indicate what is returned and how a false 'unveraenderter_zeitbezug' affects the outcome. Neither is addressed, so an agent can pass valid arguments without knowing what to expect back.

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 each of the four parameters is already documented in the schema (laufende, kontrollzeit, neuer_eintrag, unveraenderter_zeitbezug). The description contributes no additional meaning about range constraints, units, or how the timestamps interact, so the baseline 3 is appropriate.

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 names an operation ('trennen' / 'Separate') and an object (residual debris vs. later arrivals within marked areas), so it is not a pure tautology. But it never says what the tool produces — a boolean verdict, a corrected timestamp, or a labeled interval — which is the crux of a tool named 'neuer_schmutzeintrag_nach_lauf'. The English clause largely restates the German without adding precision.

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 or when-not-to-use guidance. The many sibling tools (e.g. poolreinigung_gleiches_raster_zwei_beobachtende) suggest a family of similar temporal comparisons, yet the description names no alternative and states no condition under which this one should be selected over them.

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