Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_reset_und_eigene_einrichtung_trennen

Read-only

Eine behauptete Rücksetzung von der praktisch bestätigten Ersteinrichtung beim Besitzerwechsel trennen — Verify device handover state without collecting account information.

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": {
      "bisherige_kopplung": "<bisherige_kopplung>",
      "lokaler_start": "<lokaler_start>",
      "funktionen_konto_noetig": "<funktionen_konto_noetig>",
      "eigene_einrichtung_bestaetigt": "<eigene_einrichtung_bestaetigt>"
    },
    "name": "gebrauchtgeraet_reset_und_eigene_einrichtung_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
lokaler_startYesWurde der laut Anleitung reguläre Start ohne Bindung praktisch beobachtet?
bisherige_kopplungYesBelegter Zustand der bisherigen Kontobindung.
funktionen_konto_noetigYesBraucht der gewünschte eigene Ablauf laut Anleitung eine Einrichtung mit Konto?
eigene_einrichtung_bestaetigtYesWurde die vorgesehene eigene Einrichtung bereits 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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a privacy constraint ('without collecting account information') and an evidence distinction between claimed and practically confirmed states, but it does not explain the verification logic or return decision.

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 description is compact and front-loads the core operation before the English clarification. The bilingual rendering is slightly redundant, but the English sentence adds a distinct privacy constraint rather than merely repeating the German clause.

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?

With full schema coverage and read-only annotations, the main missing piece is the output semantics: no output schema exists, and the description does not specify what the verification returns or how the decision categories are represented. For an assessment tool, that is a meaningful 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 description coverage is 100%, with all four parameters documented and one enum fully described. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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: separating a claimed reset from a practically confirmed initial setup during owner change, and frames it as verifying handover state. It is clear enough to distinguish from generic device tools, but it does not explicitly differentiate itself from the many sibling gebrauchtgeraet_* 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?

It provides a contextual use case ('Verify device handover state without collecting account information') and implies an owner-change scenario, but gives no explicit when-not-to-use guidance or named alternatives. Usage must be inferred from the purpose statement.

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