Skip to main content
Glama

getecoback-climate-weather

bodenpflege_referenzstellen_gegenprobe

Read-only

Die Wiedererkennbarkeit sichtbarer Stellen mit unbearbeiteten Referenzstellen prüfen. — Check visibility against untouched reference marks.

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": {
      "teststellen": "<teststellen>",
      "teststellen_unsichtbar": "<teststellen_unsichtbar>",
      "referenzstellen": "<referenzstellen>",
      "referenzstellen_unsichtbar": "<referenzstellen_unsichtbar>"
    },
    "name": "bodenpflege_referenzstellen_gegenprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
teststellenYesMarkierte, im Test bearbeitete Stellen.
referenzstellenYesBearbeitungsfreie Referenzstellen mit ähnlichen sichtbaren Spuren.
teststellen_unsichtbarYesBearbeitete Stellen, die bei der Nachkontrolle unsichtbar waren.
referenzstellen_unsichtbarYesDavon bei der Nachkontrolle unsichtbare Referenzstellen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safe read-only, closed-world profile, so the description's main added value is the cross-check concept itself. It does not explain what the tool returns (a ratio, a verdict, a count?), whether the four counts must be internally consistent, or what happens with zero test spots — gaps that matter for a pure computation.

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 sentences with the core idea front-loaded and no filler. The bilingual restatement is mildly redundant, but it is functional rather than padding.

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?

All four parameters are required and fully described, and the safety profile is covered by annotations. However, with no output schema, the description should say what the result looks like (ratio, boolean verdict, report) and how the four counts combine, which is left entirely implicit.

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 counts is already documented in the schema, and the description adds no format, relationship, or constraint details beyond the schema. Baseline 3 is appropriate here.

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?

States a concrete operation (check recognizability/visibility of treated spots against untreated reference spots) with a named comparison method, so an agent knows roughly what computation happens. It does not, however, distinguish itself from the closely named sibling bodenpflege_sichtspuren_trockenprobe or explain how the two differ.

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, when-not-to-use, or alternative-selection guidance. The comparison framing implies a context (a cross-check pass after treatment), but the agent must infer that entirely, and nothing tells it when this tool is preferred over the dry-run sibling.

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