Skip to main content
Glama

getecoback-raumklima

backofenzubehoer_entnahmebereich_vollstaendige_uebung

Read-only

Bei kalter Probe feststellen, ob ein bereits freier Auszug auch den geplanten zweiten Handgriff zulässt — Distinguish reaching a tray from completing the intended check.

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": {
      "pruefaufbau_belegt": "<pruefaufbau_belegt>",
      "griffpunkt_erreicht": "<griffpunkt_erreicht>",
      "vorderer_bereich": "<vorderer_bereich>",
      "hinterer_bereich": "<hinterer_bereich>",
      "hinten_erforderlich": "<hinten_erforderlich>"
    },
    "name": "backofenzubehoer_entnahmebereich_vollstaendige_uebung"
  }
}

Input Schema

NameRequiredDescriptionDefault
hinterer_bereichYesSelbst beobachteter Zugriff im hinteren Bereich.
vorderer_bereichYesSelbst beobachteter Zugriff im vorderen Bereich.
pruefaufbau_belegtYesGerät, Auszug, Blech und zwei zusammengehörige Handgriffe wurden im kalten Vergleich bestätigt.
griffpunkt_erreichtYesWurde der erste Griffpunkt tatsächlich erreicht?
hinten_erforderlichYesIst der hintere Handgriff für den beabsichtigten Ablauf notwendig?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds that this is an assessment performed against an observed cold-test setup, and that partial success (reaching the tray) is distinct from full success (completing the check) — useful behavioral framing. It does not say what verdict is produced or how conflicting observations (e.g. 'offen' values) are resolved, which matters for a judgment-style tool.

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?

Two compact clauses, with the operative condition ('Bei kalter Probe feststellen, ob...') front-loaded and the discriminating distinction placed after the dash. The bilingual split and the slight overlap between 'geplanten zweiten Handgriff' and 'completing the intended check' cost a little, but there is no 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 read-only assessment tool with five required inputs and no output schema, the description should indicate the shape of the conclusion it reaches, since nothing else documents the return value. It conveys the question being answered but not the form of the answer or how the enum states combine into a verdict. Enough to call the tool, not enough to fully anticipate its result.

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 coverage is 100%, so all five parameters are already documented, and the baseline is 3. The description does add a conceptual mapping — 'bereits freier Auszug' to the confirmed front/back access fields and 'geplanter zweiter Handgriff' to hinten_erforderlich — but it never states this mapping explicitly per field, so the added meaning is suggestive rather than substantive.

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 and object: during a cold probe ('Bei kalter Probe'), determine whether an already-free pull-out permits the planned second handle. The closing clause 'Distinguish reaching a tray from completing the intended check' sharpens the purpose beyond the tool name's generic 'vollstaendige_uebung'. It is clear about what is being assessed, though the domain vocabulary is idiosyncratic enough that an agent still has to map it onto the five parameters.

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 kalter Probe' supplies one precondition for use, which is genuine context. However, no when-not condition, prerequisite state, or alternative sibling tool is named, so the usage boundary is implied rather than stated. It is adequate minimum-viable guidance but leaves the agent to infer when this check applies versus adjacent checks.

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