Skip to main content
Glama

getecoback-climate-weather

oekodesign_standby_anwendungsbereich_kueche

Read-only

Bei einem genauen Haushaltsmodell den allgemeinen Standby-Rahmen von ausdrücklich produktspezifischen Regelungen trennen — Identify which rule family a confirmed kitchen appliance belongs to.

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": {
      "art": "<art>",
      "markt_datum": "<markt_datum>",
      "haushaltszweck_belegt": "<haushaltszweck_belegt>",
      "netzstrom_benoetigt": "<netzstrom_benoetigt>",
      "nennspannung_bis_250_v_belegt": "<nennspannung_bis_250_v_belegt>"
    },
    "name": "oekodesign_standby_anwendungsbereich_kueche"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesBelegte Geräteart und gegebenenfalls bestätigte Spezialverordnung.
markt_datumYesBelegtes EU-Inverkehrbringen oder Inbetriebnehmen nach einschlägigem Bezug, kein Kaufdatum. YYYY-MM-DD, leer wenn offen.
netzstrom_benoetigtYesIst das genaue Gerät laut Unterlage für seine bestimmungsgemäße Funktion auf das Versorgungsnetz angewiesen?
haushaltszweck_belegtYesFür Haushaltszweck ausgelegt, geprüft und vermarktet, konkrete Variante bestätigt?
nennspannung_bis_250_v_belegtYesBelegt die Unterlage Nennspannung höchstens 250 V für dieses Modell?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that the tool performs a scope-classification step, but it does not explain the form of the result, how ambiguous cases are handled, or what happens when the enum value 'offen' is supplied.

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 two short sentences, front-loading the core classification intent. The bilingual restatement is slightly redundant but still efficient and free of filler.

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 five-parameter, fully required classification tool with no output schema, the description should explain what kind of result (e.g., a rule-family label or decision outcome) is returned. It conveys the purpose but leaves the output and edge-case behavior underspecified.

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 all five parameters, including the enum values and date format, are already documented in the schema. The description adds no further meaning about individual parameters beyond what the schema provides, making the baseline score appropriate.

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 classification action: separating the general standby framework from product-specific rules for a confirmed kitchen appliance. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as oekodesign_standby_energiesparzeit_geraetefall or oekodesign_standby_leistungsreferenz_stichtag.

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?

The phrase 'Bei einem genauen Haushaltsmodell' implies the prerequisite of a precise, confirmed model, which gives some context for when to use it. However, there is no explicit when-not guidance and no named alternatives or routing rules among the many standby-related sibling tools.

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