Skip to main content
Glama

getecoback-climate-weather

rasenroboter_randprobe_referenzpunkt_vor_nach

Read-only

Wiederkehrende Reststellen an zwei bereits dokumentierten Rasenrändern gezielt nachbeobachten — Separate recurring edge observations from one-off 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": {
      "a_beide": "<a_beide>",
      "a_nur_zweite": "<a_nur_zweite>",
      "b_beide": "<b_beide>",
      "b_nur_zweite": "<b_nur_zweite>",
      "referenzpunkte_gleich": "<referenzpunkte_gleich>"
    },
    "name": "rasenroboter_randprobe_referenzpunkt_vor_nach"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_beideYesAm ersten Rand in beiden begleiteten Proben beobachtete Reststellen.
b_beideYesAm zweiten Rand in beiden Proben beobachtete Reststellen.
a_nur_zweiteYesAm ersten Rand nur in der zweiten Probe beobachtete Reststellen.
b_nur_zweiteYesAm zweiten Rand nur in der zweiten Probe beobachtete Reststellen.
referenzpunkte_gleichYesGleiche feste Punkte und vergleichbare Sicht in beiden Proben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds little beyond the purpose: it does not explain what the tool returns, how the two-sample counts are interpreted, or what happens when referenzpunkte_gleich 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?

The description is front-loaded and very short, with the core observation target stated first. The English sentence largely restates the German sentence, which is mildly redundant but not harmful.

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?

For a five-parameter comparison tool with no output schema, the definition is too sparse. It does not explain the result, how the count combinations are used, or how the required boolean affects behavior, leaving an agent to infer the tool's actual computational semantics.

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 the input schema already defines all five parameters, including the two-edge and two-sample count categories and the reference-point comparability flag. The description adds the recurring-versus-one-off framing but no parameter-specific meaning beyond the schema.

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 states a specific action and scope: targeted follow-up observation of recurring residual spots on two already documented lawn edges, and explicitly says it separates recurring observations from one-off marks. It is clear enough to distinguish this from generic recording, but it does not name or distinguish any sibling comparison tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context: use it when residual spots recur at two documented edges and you need to separate recurring from one-off marks. It does not provide explicit when-not guidance or name alternative tools, so it falls short of a 5.

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