Skip to main content
Glama

getecoback-raumklima

oekodesign_reparatur_geraeteart_anwendungsbeleg

Read-only

Geräteart, Ausnahme und dokumentiertes EU-Inverkehrbringen für die beiden genannten Verordnungen zusammen prüfen — Check the scope evidence for the two household appliance repair annexes.

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>",
      "ausnahme": "<ausnahme>",
      "eu_datum": "<eu_datum>"
    },
    "name": "oekodesign_reparatur_geraeteart_anwendungsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesGeräteart aus der Herstellererklärung. Konventioneller Trockner bedeutet Haushaltstrockner ohne Waschfunktion.
ausnahmeYesFällt das Gerät nach geprüfter Erklärung aus dem gewählten Anwendungsbereich, etwa gewerbliche Maschinenrichtlinie oder ausschließlich Akku mit optionalem separat erworbenem Netzgleichrichter?
eu_datumYesBelegtes EU-Inverkehrbringen des betrachteten Geräts. Datum YYYY-MM-DD, leer wenn unbekannt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety is covered. The description adds that the three inputs are checked 'zusammen' as a combined scope assessment, which is useful behavioral context, but it never says what the check produces (a yes/no scope verdict? an evidence gap report?) and there is no output schema to fall back on.

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

Conciseness3/5

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

Two short sentences with no filler, but the second sentence is a plain English restatement of the first rather than new information, and the front-loaded German clause spends its most valuable words on the unresolved 'beiden genannten Verordnungen'.

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 three required parameters, no output schema, and a compliance-flavored read operation, the definition is thin: it identifies the inputs but not the regulations in scope, nor what conclusion the check returns. Adequate to attempt a call, insufficient to interpret the outcome.

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 both enums are documented in-schema, so the baseline is 3. The description restates the three parameter names (Geräteart, Ausnahme, EU-Inverkehrbringen) without adding format, fallback, or interaction semantics — for example what an 'offen' value or an empty eu_datum implies for the result.

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 verb 'prüfen' and the three evidence items give a rough sense of the operation, but the object of the check is referred to as 'die beiden genannten Verordnungen' — regulations that are never named anywhere in the definition. An agent knows it evaluates scope evidence but cannot tell which legal scope, nor what distinguishes it from the many sibling oekodesign_* tools.

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

Usage Guidelines2/5

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

No statement of when to call this versus an alternative, no prerequisites, and no exclusions. The sibling list contains several oekodesign and reparatur tools, yet the description offers no routing signal at all; the agent must guess from the name alone.

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