Skip to main content
Glama

getecoback-climate-weather

oekodesign_fachzugang_registrierung_anfrage_stufen

Read-only

Bei Reparaturinformationen den dokumentierten Registrierungsantrag von einer späteren Einzelanfrage unterscheiden — Track the five-day registration and one-day information reference as distinct case stages.

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>",
      "registrierung": "<registrierung>",
      "registrierung_zeit_arbeitstage": "<registrierung_zeit_arbeitstage>",
      "anfrage_gesendet": "<anfrage_gesendet>",
      "info_zeit_arbeitstage": "<info_zeit_arbeitstage>",
      "zugang_zeitraum_bestaetigt": "<zugang_zeitraum_bestaetigt>"
    },
    "name": "oekodesign_fachzugang_registrierung_anfrage_stufen"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesBestätigte Haushaltsgeräteart nach Herstellerunterlagen.
registrierungYesBelegstatus der Registrierung für die zuständige Stelle.
anfrage_gesendetYesIst nach Registrierung eine eigenständige Informationsanfrage nachweislich eingegangen?
info_zeit_arbeitstageYesBelegt gezählte Arbeitstage vom Eingang dieser Anfrage bis Antwort oder Stichtag.
zugang_zeitraum_bestaetigtYesFachrolle, Geltung und Zeitfenster für diese Reparaturinformationen sind bereits belegt?
registrierung_zeit_arbeitstageYesBelegt gezählte Arbeitstage seit Eingang des Registrierungsantrags bis Antwort oder Stichtag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 the substantive behavioral point that the two day counts are evaluated as distinct case stages rather than a single cumulative clock, which is genuine context, but it says nothing about the outcome of that comparison or how the boolean flags affect it.

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?

A single sentence, front-loaded with the domain context, with no filler. The German/English duplication restates the same content rather than adding information, which is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six required parameters and no output schema mean the description must carry the burden of explaining what the returned judgement looks like. It leaves the core question — what result the stage comparison yields and how the confirmed/not-sent flags change it — unanswered, which is a serious gap for a six-parameter assessment tool.

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 baseline is 3. The description contributes a small amount beyond the schema by tying the day-count parameters to a five-day registration reference and a one-day information reference, hinting at thresholds, but it does not state whether those are the comparison limits or just naming conventions.

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 names the domain (repair information) and the conceptual job — keeping a documented registration application separate from a later individual inquiry — but the operative verb is only 'distinguish/track', so it is unclear whether the tool validates, computes, or classifies the stages. It never says what it produces, and no sibling is named for contrast.

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?

'Bei Reparaturinformationen' implies the situation in which the tool applies, so usage is inferable. There is no explicit when-not condition, no prerequisite (e.g. confirmed role/time window) stated as a gating rule, and no alternative tool named.

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