Skip to main content
Glama

getecoback-climate-weather

spuelstatus_restzeit_und_echte_enduhrzeit_abgleich

Read-only

Eine abgelesene Restzeit zur selben Uhrzeit mit dem später tatsächlich beobachteten Ende abgleichen — Compare a displayed expectation with a separately observed completion event.

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": {
      "ablesung_min": "<ablesung_min>",
      "restanzeige_min": "<restanzeige_min>",
      "ende_min": "<ende_min>",
      "lauf_ohne_ersatz": "<lauf_ohne_ersatz>"
    },
    "name": "spuelstatus_restzeit_und_echte_enduhrzeit_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_minYesUhrzeit des beobachteten Ende-Markers auf derselben Zeitachse.
ablesung_minYesZeitpunkt, an dem eine Restzeit abgelesen wurde.
restanzeige_minYesDamals angezeigte Restzeit in Minuten.
lauf_ohne_ersatzYesDie Anzeige und das abgelesene Ende waren nachweislich derselbe Lauf und kein neuer Start.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false. The description adds the comparison context (displayed expectation versus separately observed completion) but does not disclose what the comparison returns, how mismatches are represented, or what the 'lauf_ohne_ersatz' condition changes in the result. No contradiction with annotations is present.

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 short and front-loaded with the core comparison. The English sentence is essentially a translation rather than new information, so it is slightly redundant, but not enough to undermine clarity.

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 purpose and required inputs are covered, and annotations make the safety profile clear. However, there is no output schema and the description does not explain the comparison result or mismatch behavior, which are important for a comparison tool; sibling-selection guidance is also absent.

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%, so all four parameters are already documented, including the same-time-axis constraint and the same-run boolean. The description reinforces the expected-versus-observed framing but adds no syntax, units, or edge-case meaning beyond the schema, so the baseline 3 is appropriate.

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 ('abgleichen' / 'Compare') and a specific resource: an observed remaining-time reading versus the later actually observed end. It is clear what the tool does, but it does not explicitly differentiate itself from the many sibling Spuelstatus tools, so it stops short of a 5.

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 intended scenario is implied by 'Eine abgelesene Restzeit zur selben Uhrzeit mit dem später tatsächlich beobachteten Ende abgleichen', but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. For an agent choosing among numerous Spuelstatus siblings, this leaves selection partly to inference.

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