Skip to main content
Glama

getecoback-raumklima

saros10r_pausenzeit_und_schlafzustand

Read-only

Ordne eine nach längerer Pause beobachtete Anzeige dem dokumentierten Schlafzustand statt einer vermuteten Störung zu — Interpret the Saros pause timeline independently of the charger

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": {
      "modell_bestaetigt": "<modell_bestaetigt>",
      "aufladung": "<aufladung>",
      "pause_min": "<pause_min>",
      "dokumentierter_zustand": "<dokumentierter_zustand>",
      "pause_ohne_fehlerhinweis": "<pause_ohne_fehlerhinweis>"
    },
    "name": "saros10r_pausenzeit_und_schlafzustand"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufladungYesDer Roboter wurde während des fraglichen Zeitraums aufgeladen
pause_minYesLückenlos dokumentierte Minuten seit Beginn einer normalen Pause
modell_bestaetigtYesSaros 10R · S91COP auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
dokumentierter_zustandYesWirklich am Roboter beobachteter letzter Zustand
pause_ohne_fehlerhinweisYesGleiche normale Pause, ohne gesonderte Fehlermeldung oder erneuten Auftrag

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 the safety profile is covered. The description adds a real interpretive rule – favor the documented sleep state over a suspected malfunction, and treat the charger as irrelevant to the conclusion. This slightly conflicts with the required 'aufladung' parameter, which records charger state: the description tells the agent the charger should not drive the diagnosis while the schema mandates supplying it, a tension the description does not resolve. It also says nothing about what verdict or output form the tool produces.

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 German sentence followed by a short English scoping clause – the decision rule is front-loaded and there is no filler. The bilingual restatement is mildly redundant but clarifies scope rather than repeating the name. Well-sized for a five-parameter classifier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description bears some burden for return values, and it does indicate the intended conclusion – a mapping to the documented sleep state instead of a fault. Combined with a fully described schema and read-only annotations, an agent has enough to invoke it correctly. The unresolved role of the charger parameter and the absence of any output shape keep it from a 5.

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%: all five parameters carry descriptions, two have enumerated values, and bounds like 0–1440 minutes and the model confirmation requirement are spelled out in the schema. The description therefore has little left to add beyond echoing the pause and documented-state concepts. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific action: attribute an observed display state seen after a longer pause to the documented sleep state rather than a suspected fault, scoped to the Saros pause timeline. The verb+resource are concrete enough that an agent can tell this is a diagnostic/classification step, not an inspection or maintenance action like the sibling drying or dock tools. It stops short of 5 because it never names a contrasting sibling or bounds the tool against adjacent Saros checks.

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?

Usage context is implied by 'nach längerer Pause beobachtete Anzeige' – it applies when a display state was observed during a long pause. The clause 'independently of the charger' functions as a scope constraint on interpretation. However, there is no explicit when-not guidance and no named alternative to pick instead, so the agent must infer selection from scenario fit alone.

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