Skip to main content
Glama

getecoback-climate-weather

oekodesign_teilgruppe_rollenweg_de

Read-only

Eine genaue Teileart dem vorgesehenen Endnutzer- oder Fachreparaturweg in Deutschland zuordnen — Distinguish annex-listed consumer and possibly registered-professional part routes.

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>",
      "teil": "<teil>",
      "rolle": "<rolle>",
      "geltung_bestaetigt": "<geltung_bestaetigt>"
    },
    "name": "oekodesign_teilgruppe_rollenweg_de"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesBestätigte Haushaltsgeräteart nach Herstellerunterlagen.
teilYesGenaue belegte Teilart. Rohrleitungszubehör umfasst darin benannte Schläuche, Ventile, Filter und Aquastops.
rolleYesRolle der anfragenden Partei.
geltung_bestaetigtYesKonkrete Modellvariante und Geltung der angegebenen Verordnung bereits belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish read-only and closed-world behavior, and the description adds that the mapping is Germany-specific and distinguishes annex-listed consumer versus possibly registered-professional routes. However, it does not describe the return format, ambiguity handling such as 'nicht_eindeutig', or how 'geltung_bestaetigt' affects 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.

Conciseness4/5

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

The description is a compact single sentence with the core German statement front-loaded and an English gloss after the dash. The bilingual format is slightly redundant but not verbose or padded.

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 classification tool with no output schema, the description supplies useful regulatory context but not the result shape or edge-case behavior. It is adequate to begin using the tool, but leaves the agent guessing about the returned route label and ambiguity handling.

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 enum values and parameter meanings are already documented. The description reinforces the exact part type and the end-user/professional route distinction, but adds no additional mapping rules beyond what the schema provides.

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 verb ('zuordnen') and resource ('genaue Teileart' to the intended end-user or professional repair route) and adds the German regulatory scope. It is identifiable as a classification/mapping tool, though it does not name a sibling alternative or explicitly distinguish itself from related 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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The required 'geltung_bestaetigt' field hints at a prerequisite, but the description does not explain when the tool should or should not be used.

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