Skip to main content
Glama

getecoback-climate-weather

pool_flaechenplan_nacharbeit_gesperrte_zonen

Read-only

Sichtbare Nacharbeit nach Poolbereichen mit und ohne bestätigten Zugang erfassen — Keep visible work needs separate from areas with unconfirmed access.

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": {
      "boden_offen": "<boden_offen>",
      "wand_offen": "<wand_offen>",
      "treppe_offen": "<treppe_offen>",
      "boden_methode_belegt": "<boden_methode_belegt>",
      "wand_methode_belegt": "<wand_methode_belegt>",
      "treppe_methode_belegt": "<treppe_methode_belegt>"
    },
    "name": "pool_flaechenplan_nacharbeit_gesperrte_zonen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wand_offenYesIst an der bezeichneten Wand sichtbare Nacharbeit offen?
boden_offenYesIst am markierten Bodenabschnitt sichtbare Nacharbeit offen?
treppe_offenYesIst an der bezeichneten Treppe sichtbare Nacharbeit offen?
wand_methode_belegtYesVorgesehene Methode und Zugang an der Wand bestätigt?
boden_methode_belegtYesVorgesehene Methode und Zugang am Boden bestätigt?
treppe_methode_belegtYesMethode und Zugang an der Treppe bestätigt?

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. The description adds the behavioral rule that work with unconfirmed access should be kept separate, which is genuinely useful, but it never explains what the tool returns, how the three '*_offen' and three '*_methode_belegt' booleans combine into a result, or what happens when access is unconfirmed. 'Erfassen' also sits in mild tension with a purely read-only operation, since it connotes recording data that readOnlyHint says is not persisted.

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, front-loaded purpose followed by a clarifying separation principle, with no padding. The German/English duplication is translation rather than bloat, though it does take up space that could have carried actual guidance.

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?

The tool takes six required booleans and has no output schema, so the description carries the burden of explaining what a caller gets back — and it does not. An agent knows the conceptual intent (separate confirmed-access work from unconfirmed) but not the decision logic, the return shape, or how to interpret the result for planning.

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 boolean carries a German question clarifying what it asserts (visible rework open / method and access confirmed per surface). The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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 a verb-and-resource pair ('sichtbare Nacharbeit nach Poolbereichen ... erfassen'), but 'erfassen' is ambiguous because the six boolean inputs suggest an assessment/classification tool rather than one that records anything. The clarifying clause about separating work with confirmed vs. unconfirmed access narrows intent somewhat, yet no sibling tool is referenced, so an agent cannot tell this apart from the many other '*_nacharbeit_*' tools on name alone.

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 explicit when-to-use guidance, no prerequisites, and no named alternative among the dozens of sibling tools covering rework and zone topics. The description only implies usage through the phrase 'Nacharbeit nach Poolbereichen', which is too thin to route an agent between this and, for example, roboter_nacharbeit_ersatzroute or saugwischer_wendemanoever_nacharbeit.

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