Skip to main content
Glama

getecoback-raumklima

kuechengeraet_ersatzmethode_bereitschaft

Read-only

Die im Alltag verfügbare Ersatzmethode nach einem belegten Küchengerät anhand echter Einsätze prüfen. — Evaluate fallback readiness from observed kitchen appliance conflicts.

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": {
      "belegungskonflikte": "<belegungskonflikte>",
      "direkt_ersetzt": "<direkt_ersetzt>",
      "nach_vorbereitung_ersetzt": "<nach_vorbereitung_ersetzt>"
    },
    "name": "kuechengeraet_ersatzmethode_bereitschaft"
  }
}

Input Schema

NameRequiredDescriptionDefault
direkt_ersetztYesDavon mit der bestehenden Ersatzmethode ohne zusätzliche Vorbereitung erledigte Aufgaben.
belegungskonflikteYesBeobachtete Fälle, in denen das zuerst gewählte Gerät belegt war.
nach_vorbereitung_ersetztYesWeitere mit der bestehenden Ersatzmethode erst nach Vorbereitung erledigte Aufgaben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds only the framing "anhand echter Einsätze"; it never says what is actually computed from the three counts (a ratio? a threshold verdict?) or what the caller receives, which is the behavior that matters for a pure calculation tool with no output schema.

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 short sentences, one German and one English, with the action front-loaded and no filler. The bilingual duplication is intentional and does not obscure the core statement.

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?

The inputs are fully covered by the schema, but for a three-parameter computation with no output schema and no explanation of the resulting metric, the description leaves the agent guessing at what 'readiness' means and what comes back. It should state at minimum the shape of the returned assessment.

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 each of the three counts documented in the schema itself, so the baseline is 3. The description's "anhand echter Einsätze" loosely gestures at the observed-conflict input but adds no interpretation of how the counts relate to the readiness judgement.

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 names a specific action ("Ersatzmethode ... prüfen" / "Evaluate fallback readiness") and the evidence basis ("belegtes Küchengerät" / "observed kitchen appliance conflicts"), so an agent can tell this is an assessment computed from observed fallback usage. It stops short of naming which sibling to prefer, but the verb+resource pairing is unambiguous.

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 statement of when to call this versus any other analysis tool, no prerequisites, and no exclusions. The phrase "nach einem belegten Küchengerät" weakly implies a post-conflict scenario, but the agent must infer the trigger condition entirely.

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