Skip to main content
Glama

getecoback-raumklima

betriebszustand_funktion_led_uhr_netzausloeser

Read-only

Einen beobachteten Geräteabschnitt nach aktiver Hauptfunktion, Anzeige und bestätigtem Auslöser einordnen — Classify documented function evidence rather than guessing standby from wattage or a light.

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": {
      "versorgungsnetz": "<versorgungsnetz>",
      "hauptfunktion": "<hauptfunktion>",
      "sichtfunktion": "<sichtfunktion>",
      "ausloeser": "<ausloeser>",
      "andere_funktionen_ausgeschlossen": "<andere_funktionen_ausgeschlossen>"
    },
    "name": "betriebszustand_funktion_led_uhr_netzausloeser"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausloeserYesDokumentierte verfügbare Wiederaufnahme-Funktion. Ein Symbol allein zählt nicht als Nachweis.
hauptfunktionYesWar eine Hauptfunktion im aufgezeichneten Abschnitt aktiv?
sichtfunktionYesEindeutig dokumentierte sichtbare Funktion. Uhr oder Information bezeichnet hier eine kontinuierliche Anzeige, unabhängig von der Leistungsaufnahme.
versorgungsnetzYesWar das Gerät laut bestehendem Protokoll mit dem Stromnetz verbunden?
andere_funktionen_ausgeschlossenYesSind andere Funktionen außer der beschriebenen Anzeige, belegt verfügbarer Reaktivierung und EMV-Funktionen ausgeschlossen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a meaningful epistemic constraint (evidence-based classification, no inference from wattage or a light), but says nothing about the shape of the result or what an 'offen' value implies for downstream decisions.

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 tight clauses: the action first, then the anti-pattern it guards against. Slight redundancy in pairing a German verb with its English gloss, but no wasted sentences and the guiding constraint is front-loaded.

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?

For a read-only classifier with five fully documented enum parameters, the description covers purpose, evidentiary requirement, and the main misuse it prevents. Since no output schema exists, one could wish for a hint about what the classification returns, but nothing essential to correct invocation is missing.

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 five parameters required and four enums richly documented, including the note that a symbol alone is not proof. The description names the three classification axes (Hauptfunktion, Anzeige, Auslöser) but adds no syntax or interpretation beyond what the schema already supplies, so the baseline 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?

States a specific verb (einordnen/classify) and a specific resource (an observed device section, judged by active main function, display, and confirmed trigger), so the operation is unambiguous. It also implicitly separates itself from the wattage-based sibling by rejecting 'guessing standby from wattage', though it never names that alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear condition of use: classify when documented function evidence exists, not when only wattage or a lit lamp is available. The exclusion is stated conceptually rather than by naming a sibling tool, so an agent knows the boundary but must map it to alternatives itself.

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