Skip to main content
Glama

getecoback-raumklima

backofenzubehoer_nur_ersetzen_wenn_funktion_fehlt

Read-only

Den Wunsch nach einem Auszug gegen einen anhand eigener Handgriffe belegten tatsächlichen Bedarf prüfen — Separate a genuine access gap from a feature already provided by existing equipment.

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": {
      "anforderungen_belegt": "<anforderungen_belegt>",
      "zugriff_noetig": "<zugriff_noetig>",
      "zugriff_vorhanden": "<zugriff_vorhanden>",
      "zweite_ebene_zeitgleich": "<zweite_ebene_zeitgleich>",
      "beide_ebenen_vorhanden": "<beide_ebenen_vorhanden>"
    },
    "name": "backofenzubehoer_nur_ersetzen_wenn_funktion_fehlt"
  }
}

Input Schema

NameRequiredDescriptionDefault
zugriff_noetigYesIst herausziehbarer Zugriff für den eigenen Zweck erforderlich?
zugriff_vorhandenYesBeobachtung zum herausziehbaren Zugriff am vorhandenen bestätigten Zubehör.
anforderungen_belegtYesSind zwei eigene Aufgaben und die tatsächlich vorhandene passende Ausrüstung überprüft?
beide_ebenen_vorhandenYesBeobachtung am tatsächlich vorhandenen und passend zugeordneten Aufbau.
zweite_ebene_zeitgleichYesMuss der eigene Ablauf eine zweite Ebene zur selben Zeit erreichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 substantive context about what is being judged (demonstrated need vs. already-present equipment), but for an evaluation-style tool it says nothing about what the result looks like, whether a verdict is returned, or how the checked criteria combine.

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?

It is a single front-loaded sentence pair with no filler, and the core criterion comes first. The German and English clauses restate the same content verbatim, and the abstract phrasing ("eigene Handgriffe", "zweite Ebene") forces the reader to cross-reference the schema to make it concrete.

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?

Five required parameters, two enums, and no output schema mean the description should clarify what the tool returns and how the five inputs drive the verdict. It covers the intent adequately but leaves the result semantics entirely unexplained for a decision tool whose whole value is 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%, with every parameter and both enums documented in German, so the schema does the heavy lifting. The description gestures at the evidence criterion ("anhand eigener Handgriffe belegten tatsächlichen Bedarf"), which loosely maps to anforderungen_belegt, but adds no interpretation of the enum states or of how the two observation fields relate.

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 ("prüfen"/separate) and a specific decision object: a wish for a pull-out ("Auszug") versus a need demonstrated through one's own handling tasks. It is meaningfully more informative than the opaque name, but it never names or contrasts the closest siblings (e.g. backofenzubehoer_entnahmebereich_vollstaendige_uebung, backofenzubehoer_nachkauf_bestand_eigenes_exemplar), so an agent cannot fully route between them from the text alone.

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 trigger is implied — apply this check when someone wants an extract/pull-out — and the framing "separate a genuine access gap from a feature already provided" hints at the negative case. However, there is no explicit when-not guidance, no stated prerequisites, and no pointer to any alternative tool for the adjacent scenarios the siblings cover.

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