Skip to main content
Glama

getecoback-climate-weather

spuelstatus_unterbrechung_fortsetzung_neustart_abgrenzen

Read-only

Eine beobachtete Spülpause von einem Abbruch oder bestätigten Folgelauf unterscheiden — Keep resumed operation distinct from a newly identified run.

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": {
      "pause_oder_abbruch": "<pause_oder_abbruch>",
      "fortsetzung_belegt": "<fortsetzung_belegt>",
      "neuer_start_belegt": "<neuer_start_belegt>",
      "ende_vor_ereignis": "<ende_vor_ereignis>"
    },
    "name": "spuelstatus_unterbrechung_fortsetzung_neustart_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_vor_ereignisYesEnde des ursprünglichen Laufs vor dem Ereignis separat belegt.
fortsetzung_belegtYesDer exakt selbe Lauf ist als fortgesetzt unabhängig belegt.
neuer_start_belegtYesEin separater, neuer Programmstart ist für den nächsten Eintrag separat belegt.
pause_oder_abbruchYesTatsächlich protokollierter Zustand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the useful idea that every claim must be separately evidenced (bestätigt/belegt), but it never states what the tool returns or how conflicting evidence is resolved — a real gap since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, which is good, but the German statement is echoed in English, consuming half the text with a near-duplicate rather than adding new information. The redundant bilingual restatement is the main structural weakness.

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

Completeness2/5

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

For a four-required-boolean decision tool with no output schema, the description should explain what classification is produced and how the evidence flags combine. Instead it only restates the intent twice, leaving the agent unsure what a call yields or what to do when pause_oder_abbruch is 'unbekannt'.

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 each of the four parameters is already documented, which sets the baseline at 3. The phrase 'keep resumed operation distinct from a newly identified run' hints at the fortsetzung_belegt versus neuer_start_belegt contrast, but adds no precedence rules or guidance on how to set ambiguous combinations.

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 operation — distinguishing an observed rinse pause (beobachtete Spülpause) from an abort or a confirmed subsequent run — with a clear verb (unterscheiden) and resource. It does not differentiate itself from siblings such as spuelstatus_ende_um_timer_ende_zeittext_unterscheiden, so an agent must infer the boundary from the name alone.

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 is implied by the framing: this is the tool to reach for when a rinse pause has been observed and its nature is ambiguous. There is no explicit when-not guidance, no prerequisites, and no named alternative for cases where the evidence is already conclusive.

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