Skip to main content
Glama

getecoback-raumklima

poolreinigung_gleiches_raster_zwei_beobachtende

Read-only

Beim Auswerten zweier Sichtnotizen zum gleichen Poolabschnitt bestätigte und widersprüchliche Funde getrennt ausweisen — Preserve observer agreement rather than pooling their counts.

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": {
      "a_funde": "<a_funde>",
      "b_funde": "<b_funde>",
      "deckung": "<deckung>",
      "eintraege_zeitgleich": "<eintraege_zeitgleich>"
    },
    "name": "poolreinigung_gleiches_raster_zwei_beobachtende"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_fundeYesVon Person A am selben Raster markierte sichtbare Stellen.
b_fundeYesVon Person B markierte sichtbare Stellen.
deckungYesDurch Abgleich der Rasterpositionen bestätigte gleiche Funde.
eintraege_zeitgleichYesZeitfenster, Raster und Bewertungsregel in beiden Notizen gleich?

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 safety is covered. The description adds the meaningful behavioral point that this preserves observer agreement instead of pooling counts, but says nothing about what the response contains (two counts? a verdict?) or what happens when eintraege_zeitgleich is false.

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?

One sentence with the purpose front-loaded, followed by a short contrast clause that earns its place by clarifying the non-pooling intent. The German/English mix is a minor readability cost but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, fully-described, read-only comparison with no output schema, the description gives enough to call it correctly. The main gap is the significance of the eintraege_zeitgleich gate and the shape of the separated findings, neither of which is explained.

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 coverage is 100%, so all four parameters are already documented in the schema. The description adds no format, range, or role detail beyond that, so the baseline 3 applies.

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: evaluating two sighting notes for the same pool section and separately reporting confirmed versus contradictory findings. That is concrete enough for an agent to know what the tool computes, though it never differentiates itself from the many 'two observations compared' siblings.

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 contrast clause 'Preserve observer agreement rather than pooling their counts' implies the tool is for cases where per-observer agreement matters and aggregation would be wrong, but it never states a when-not condition or names an alternative tool. Usage is only implied.

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