Skip to main content
Glama

getecoback-raumklima

poolroboter_treppenumkehr_sichtprotokoll

Read-only

Beobachtete Umkehr, Weiterfahrt und fehlende Sicht an einer freigegebenen Treppenzone trennen — Record observed turn-backs separately from blind spots at an approved transition.

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": {
      "annaeherungen": "<annaeherungen>",
      "umkehr": "<umkehr>",
      "fortgesetzt": "<fortgesetzt>",
      "genaue_treppenzone_belegt": "<genaue_treppenzone_belegt>"
    },
    "name": "poolroboter_treppenumkehr_sichtprotokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
umkehrYesAnfahrten mit vollständig sichtbarer Umkehr vor dem Übergang.
fortgesetztYesAnfahrten mit vollständig sichtbarer Fortsetzung in den bestätigten Bereich.
annaeherungenYesBeobachtete Anfahrten zur bezeichneten Zone.
genaue_treppenzone_belegtYesIst dieser Übergang für das genaue Modell nach Anleitung bestätigt?

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 state readOnlyHint=true and openWorldHint=false, so the safety profile is supplied externally. The description adds the approved-transition precondition and the separation of observed categories, but it does not clarify whether 'Record' means persist data or simply report/classify observations, which is a meaningful ambiguity for an agent.

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 observed categories before the approved-zone condition. The bilingual duplication is somewhat redundant and the English rendering is not a complete translation, but the description remains short and readable.

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?

The tool has four required parameters, full schema descriptions, no output schema, and read-only annotations. The description explains the domain scenario, but it does not explain the output or what the agent should expect after supplying counts and the approval boolean, leaving a moderate completeness gap.

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 all four parameters are fully described in the schema and the description does not need to restate them. It mentions turn-backs, continued travel, and missing visibility in German, but the English sentence omits continued travel and adds no syntax or validation detail 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 gives a specific verb-and-resource combination: record observed turn-backs separately from blind spots at an approved transition. It is clear enough to distinguish this as an observation/protocol tool, but it does not explicitly differentiate itself from nearby pool-robot evidence 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 phrase 'an einer freigegebenen Treppenzone' implies the tool applies only to an approved stair/transition zone, which is useful context. However, there is no explicit when-not guidance and no named alternative such as poolroboter_umkehrabweichung_beckenvariante_beleg.

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