Skip to main content
Glama

getecoback-raumklima

oekodesign_standby_energiesparzeit_geraetefall

Read-only

Die veröffentlichte Zeitreferenz je Anwendungsfall ausweisen und Bedingungen zur Herstellerspezifikation sichtbar halten — Select the general or coffee-machine transition reference after documenting its stated conditions.

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": {
      "fall": "<fall>",
      "rahmen_bestaetigt": "<rahmen_bestaetigt>",
      "keine_hauptfunktion_oder_abhaengigkeit": "<keine_hauptfunktion_oder_abhaengigkeit>",
      "bestimmungsgemaess_vereinbar": "<bestimmungsgemaess_vereinbar>"
    },
    "name": "oekodesign_standby_energiesparzeit_geraetefall"
  }
}

Input Schema

NameRequiredDescriptionDefault
fallYesVerifiziert zutreffende Geräteart und Netzwerkklasse laut Unterlagen.
rahmen_bestaetigtYesGeltung, Datum und Ausnahmen der Referenz sind für die betrachtete Quelle geprüft?
bestimmungsgemaess_vereinbarYesIst der Vergleich im dokumentierten vorgesehenen Gerätegebrauch mit dieser Stromsparfunktion vereinbar?
keine_hauptfunktion_oder_abhaengigkeitYesFür die betrachtete Referenzphase sind beendete Hauptfunktion und keine Abhängigkeit eines anderen energieverbrauchsrelevanten Produkts belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 that conditions must be documented before selecting and that manufacturer-specification conditions must remain visible, but it does not say what the selection returns or how the boolean gates affect the outcome.

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

Conciseness2/5

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

The definition is short but garbled: a German clause and an English clause joined by an em dash partially restate each other rather than forming one front-loaded statement. The mixed-language phrasing forces the agent to reconcile two framings of the same operation.

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 four-required-parameter, read-only gating tool with no output schema, the description covers the documentation prerequisite but not the outcome of the call or how each boolean changes it. It is adequate but leaves the practical result of selection unexplained.

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 the baseline is 3. The text only loosely maps to parameters, hinting at the 'general' and 'coffee-machine' enum branches and at the documented-conditions booleans, without adding format or interpretation guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states an intent to expose the published time reference per application case and to 'select the general or coffee-machine transition reference'. That is a recognizable verb+resource, but the German and English halves frame it differently (report vs. select), and the enum in the schema contains six cases while the text names only two, so scope is left ambiguous.

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?

'after documenting its stated conditions' implies a prerequisite ordering, and the required confirmation booleans reinforce that the framework must be checked first. However, no sibling tool is named as an alternative and no when-not-to-use condition is given, leaving the agent to infer routing.

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