Skip to main content
Glama

getecoback-raumklima

rasenroboter_zugang_zwei_routen_nachweis

Read-only

Zwei beobachtete Wege aus je zwei Teilstücken auf fehlende Wegebelege prüfen — Compare route evidence where neither isolated entrance proves the whole trip.

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_eingang": "<a_eingang>",
      "a_anschluss": "<a_anschluss>",
      "b_eingang": "<b_eingang>",
      "b_anschluss": "<b_anschluss>",
      "grundstueckszugriff": "<grundstueckszugriff>"
    },
    "name": "rasenroboter_zugang_zwei_routen_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_eingangYesEinfahrt A mit dem genauen System nach Vorgabe beobachtet?
b_eingangYesEinfahrt B mit dem genauen System bestätigt?
a_anschlussYesAnschluss der Route A bis zur vorgesehenen Fläche bestätigt?
b_anschlussYesAnschluss der Route B bis zur Fläche bestätigt?
grundstueckszugriffYesIst Nutzung beider betrachteter Wege durchgängig geklärt?

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 and scope are covered by structured data. The description adds that the operation is an evidence-sufficiency comparison rather than a measurement, but it says nothing about what the check yields (e.g. which route lacks a proof) and there is no output schema to cover that.

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 compact sentence, front-loaded with the operation and resource, followed by the pivotal condition. The German/English doubling is mild redundancy but aids disambiguation for a domain-specific term; no filler or restated name/title.

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 read-only computation over five fully documented required booleans, the definition is serviceable but leaves the agent guessing what the result expresses — presumably a per-route missing-evidence verdict — since there is no output schema. The logic of why both routes must be checked jointly is stated, but not how a negative outcome is reported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so per-parameter meaning is already documented; baseline would be 3. The description goes slightly beyond by explaining that each route decomposes into exactly two pieces ('aus je zwei Teilstücken'), which tells the agent how a_eingang/a_anschluss and b_eingang/b_anschluss relate as a pair rather than as four independent flags.

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 operation (prüfen/compare) on a concrete resource (two observed routes, each made of two segments) and states the distinguishing condition 'neither isolated entrance proves the whole trip'. It is clear what the tool computes, though it does not explicitly contrast itself with the many sibling 'zwei ...' comparison tools.

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 clause 'where neither isolated entrance proves the whole trip' implicitly defines the situation in which this tool applies, which is useful routing information. However, there is no explicit when-not guidance, no mention of prerequisites, and no named alternative for the case where a single entrance sufficiency check would suffice.

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