Skip to main content
Glama

getecoback-climate-weather

stabmixer_aufsatzwechsel_stillstand_netztrennung

Read-only

Klärt, ob Stillstand und Netztrennung für einen dokumentierten gewöhnlichen Aufsatzwechsel getrennt belegt sind — Check that both a stopped drive and disconnection are documented before an attachment change.

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": {
      "geraet": "<geraet>",
      "stillstand": "<stillstand>",
      "netz_getrennt": "<netz_getrennt>"
    },
    "name": "stabmixer_aufsatzwechsel_stillstand_netztrennung"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraetYesBelegte Anleitung.
stillstandYesVollständiger Stillstand laut vorhandener Beobachtung?
netz_getrenntYesNetzstecker war laut vorhandener Beobachtung gezogen?

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 covered. The description adds the meaningful constraint that both conditions must be documented and that the change be 'ordinary', but says nothing about what verdict is returned (e.g., mixed 'offen' cases) beyond the schema's enum values.

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?

Two short clauses with the condition front-loaded and no filler. The German/English duplication is slightly redundant but aids clarity rather than hurting it.

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 three-enum, read-only check with a fully documented schema and no output schema, the definition is adequate but silent on the return value and on how 'offen' or mixed inputs are treated. That gap is small but real for a tool whose whole purpose is producing a verdict.

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% and all three parameters carry descriptions plus enums, so the schema does the heavy lifting. The description notes the two conditions must be documented separately but adds no interpretation of the 'offen' value or of how conflicting answers are resolved.

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 verb and object: it determines whether standstill and mains disconnection are separately documented ('getrennt belegt') for an ordinary attachment change. That is concrete and distinguishes the tool from the cleaning/temperature siblings, though no alternative tool is named for the case where one condition is missing.

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 only implied by the phrase 'before an attachment change'; there is no explicit when-to-use or when-not-to-use statement, and no prerequisite beyond the documented observation. An agent can infer the context but gets no explicit routing guidance.

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