Skip to main content
Glama

getecoback-climate-weather

poolroboter_wandabschnitt_anhaftung_vor_nach_probe

Read-only

Sichtbare Spuren an derselben freigegebenen Poolwand vor und nach einem Lauf erfassen — Compare marked wall residues before and after one observed pass.

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": {
      "stellen": "<stellen>",
      "vorher": "<vorher>",
      "noch_da": "<noch_da>",
      "neu_sichtbar": "<neu_sichtbar>",
      "vergleich_belegt": "<vergleich_belegt>"
    },
    "name": "poolroboter_wandabschnitt_anhaftung_vor_nach_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorherYesDavon Stellen mit sichtbarer Spur unmittelbar vorher.
noch_daYesVon den ursprünglichen Spuren danach noch sichtbare Stellen.
stellenYesMarkierte vergleichbare Sichtstellen derselben Wand.
neu_sichtbarYesZuvor unauffällige Stellen mit neuer sichtbarer Spur.
vergleich_belegtYesWaren Beleuchtung und Sichttiefe vergleichbar und Wandbereich laut Anleitung freigegeben?

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?

Annotations already declare this is a read-only, closed-world operation, so the safety profile is covered. The description adds the behavioral constraint that both observations must concern the same released wall section within one pass, but says nothing about how the comparison is reported or what happens with unmatched counts.

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 stating the measurement design, with the German and English phrasings reinforcing each other. Slightly redundant due to the bilingual restatement, but nothing is wasted.

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?

For a five-required-parameter measurement tool with no output schema, the description conveys the core protocol (same wall, before and after one pass) and the schema carries per-field meaning. It does not clarify how the counts relate to each other or what makes a comparison valid beyond the existing boolean flag.

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 five counts and the boolean comparability flag is already documented in the schema. The description's 'vor und nach einem Lauf' matches the schema meaning without adding formatting, arithmetic or validation detail beyond it.

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 concrete verb (erfassen/compare) and the exact resource and scope: visible traces on the same approved pool wall, before versus after a single observed pass. That is specific enough to separate it from generic pool checks, though it does not name any sibling tool as an alternative.

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?

Usage is implied by the phrasing 'derselben freigegebenen Poolwand' and 'vor und nach einem Lauf', which signal the required same-wall, before/after design. There is no explicit when-to-use versus when-not-to-use guidance and no named alternative among the many sibling vor_nach probes.

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