Skip to main content
Glama

getecoback-climate-weather

poolroboter_bodenraster_unbesuchte_felder

Read-only

Bekannte Bodenabschnitte nach einem beobachteten Lauf als besucht, unbesucht oder ungeprüft festhalten — Record coverage over a simple marked pool-floor grid.

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": {
      "felder": "<felder>",
      "gesehen": "<gesehen>",
      "sichtbar_ausgelassen": "<sichtbar_ausgelassen>",
      "modellbereich_bestaetigt": "<modellbereich_bestaetigt>"
    },
    "name": "poolroboter_bodenraster_unbesuchte_felder"
  }
}

Input Schema

NameRequiredDescriptionDefault
felderYesZahl gleich großer markierter Bodenfelder im ohnehin freigegebenen Bereich.
gesehenYesFelder mit mindestens einer sicher beobachteten Befahrung.
sichtbar_ausgelassenYesWährend des gesamten Laufs sichtbare Felder ohne beobachtete Befahrung.
modellbereich_bestaetigtYesSind alle markierten Felder laut Anleitung im vorgesehenen Reinigungsbereich?

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 agent knows this is a side-effect-free, closed-domain computation. The description adds the useful framing that three status classes are derived (visited / unvisited / unchecked), but it does not explain the derivation logic, whether the counts must be mutually consistent, or what the response contains. Note also a mild tension: 'festhalten' / 'Record coverage' could read as persisting state, though 'record' here plausibly means 'determine and report'; this is not a hard contradiction of readOnlyHint.

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 front-loaded sentence that states the operation before any qualifications. The German and English halves largely restate each other, which is slight redundancy, but nothing is padded or buried.

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?

Four required numeric/boolean parameters, no output schema, and only two lightweight annotations mean the description carries meaningful burden. It is enough to understand the intent but leaves open how the three statuses are computed, what consistency rules apply to the counts, and what the call returns — gaps that matter for a classification tool with no output schema.

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% and every field carries its own explanation (total marked fields, fields with an observed pass, visible-but-omitted fields, area confirmation). The description adds no per-parameter syntax, constraint, or relationship such as whether gesehen + sichtbar_ausgelassen must be ≤ felder, so it sits at the baseline.

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 and resource: capture pool-floor sections as visited, unvisited, or unchecked over a marked grid after an observed run. That is clearly more than the tool name alone, which only mentions 'unbesuchte Felder'. It does not differentiate itself from siblings such as poolroboter_beckencheck or poolroboter_treppenumkehr_sichtprotokoll, so it stops short of a 5.

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?

'nach einem beobachteten Lauf' supplies one precondition that implies this is a post-run bookkeeping step rather than a live-control call. There is no statement of when not to use it, no alternative sibling to route to for related pool checks, and no mention of how it interacts with the confirmed model-area gate.

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