Skip to main content
Glama

getecoback-raumklima

maehroboter_gartenbeobachtung_mittlere_unterbrechung

Read-only

Bei vergleichbaren begleiteten Gartenrunden beobachtete Unterbrechungen je Ursache auswerten — Compare the time spent on access pauses and other recorded stops.

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": {
      "zugang_stopps": "<zugang_stopps>",
      "zugang_min": "<zugang_min>",
      "weitere_stopps": "<weitere_stopps>",
      "weitere_min": "<weitere_min>",
      "gleiches_protokoll": "<gleiches_protokoll>"
    },
    "name": "maehroboter_gartenbeobachtung_mittlere_unterbrechung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zugang_minYesDeren beobachtete Gesamtzeit.
weitere_minYesGenehmigte, separat beobachtete Gesamtzeit dieser Pausen.
zugang_stoppsYesZahl eindeutig erkannter Pausen wegen des freigegebenen Zugangs.
weitere_stoppsYesZahl der separat beobachteten anderen Pausen.
gleiches_protokollYesWurden Start, Ende und Zuordnung bei allen Pausen gleich dokumentiert?

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, so the safety profile is clear. The description adds that this tool compares recorded stop counts and durations by cause, but it does not explain what kind of comparison result is produced or how the boolean protocol-consistency input affects the evaluation.

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 definition is compact and front-loads the comparison context before naming the counted resources. The bilingual sentence is slightly redundant but not wasteful enough to obscure the tool's purpose.

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 five-parameter comparison tool with no output schema, the description explains the observed inputs but not the return behavior or how the comparison is reported. Annotations and full schema coverage make invocation feasible, but the description stops short of fully specifying the tool's output and the role of the consistency flag.

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 the input schema already documents all five parameters, including their meanings and numeric bounds. The description reinforces the access-pause versus other-stop distinction but adds little beyond the schema and does not interpret 'gleiches_protokoll' in the description itself.

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 — evaluating/comparing observed interruptions by cause — and names the resources: access pauses and other recorded stops in comparable accompanied garden rounds. It is clear enough to distinguish this from general garden-check siblings, though it does not explicitly identify a particular sibling 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 'Bei vergleichbaren begleiteten Gartenrunden' gives an implied usage context: use this when comparing interruptions from comparable observed rounds. There is no explicit when-not guidance, no prerequisites beyond comparability, and no named alternative tool.

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