Skip to main content
Glama

getecoback-raumklima

maehroboter_gartencheck

Read-only

Passagen, Steigung und Führung vor Einsatz eines Mähroboters klären — Check narrow routes, measured slopes and navigation conditions.

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": {
      "route": "<route>",
      "slope": "<slope>",
      "signal": "<signal>"
    },
    "name": "maehroboter_gartencheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesPassage offen, eng oder unbekannt.
slopeYesSteilste Einzelabschnitte gemessen?
signalYesGrenzführung oder Empfang entlang der Route geklärt?

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 readOnlyHint=true and openWorldHint=false, consistent with a 'check' tool, so no contradiction. The description adds the pre-deployment framing but says nothing about what the check produces (verdict, recommendation, warnings) or how it handles 'unknown' inputs, leaving a meaningful gap for a no-output-schema tool.

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 front-loaded sentence that pairs the German original with an English gloss, with zero filler. The bilingual duplication costs a little space but aids comprehension rather than obscuring the point.

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 simple read-only, three-enum-parameter tool, the description covers the input dimensions adequately. But with no output schema, the agent gets no hint of what the check returns or how the three inputs combine into a result, which is the main missing piece.

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% and all three parameters are enums with their own descriptions, so the schema does the heavy lifting. The description's mention of 'Passagen, Steigung und Führung' merely restates the parameter set without adding interpretation, so 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 concrete verb and scope: pre-deployment checking of passages, measured slope, and route guidance for a robot mower. That is specific enough to distinguish it from every listed sibling (dehumidifier, heating, window topics), though it never explicitly contrasts itself with any 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?

The phrase 'vor Einsatz eines Mähroboters' gives a clear timing cue for when to call it, which is more than nothing. However, there are no exclusions, no preconditions (e.g., must slopes already be measured?), and no guidance on what to do if a value is 'unknown'.

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