Skip to main content
Glama

getecoback-raumklima

kochutensilien_set_ersatz_nur_nach_pruefung

Read-only

Ein vorhandenes Küchenwerkzeug-Set um tatsächlich freigegebene Ersatzteile ergänzen und den restlichen Mangel bestimmen — Count complete tool capacity after verified substitutes.

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": {
      "benoetigte_plaetze": "<benoetigte_plaetze>",
      "passend_vorhanden": "<passend_vorhanden>",
      "ersatz_eindeutig": "<ersatz_eindeutig>",
      "ersatz_mehrfach_zugeordnet": "<ersatz_mehrfach_zugeordnet>"
    },
    "name": "kochutensilien_set_ersatz_nur_nach_pruefung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ersatz_eindeutigYesWeitere Positionen mit je einem anderen belegbar geeigneten Ersatz.
passend_vorhandenYesDavon bereits mit nachweislich geeigneten vorhandenen Werkzeugen belegt.
benoetigte_plaetzeYesUnterschiedliche für den abgesprochenen Ablauf benötigte Positionen.
ersatz_mehrfach_zugeordnetYesWeitere Positionen, die nur demselben einzelnen Ersatz zugeordnet wurden.

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 safety is covered. The description adds the meaningful constraint that only genuinely approved substitutes count and that the residual shortfall is computed, which is real behavioral context. However, 'ergänzen' (augment a set) reads slightly like a mutation and only the second clause clarifies this is a pure counting operation, and nothing is said about the returned figure.

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 short, but the single sentence bundles two different actions and is then repeated in a mixed-language gloss that does not exactly match the German. The purpose is front-loaded enough to scan, yet the redundant second half muddies rather than sharpens.

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?

With four required numeric parameters and no output schema, the description should at minimum say what the result represents; 'den restlichen Mangel bestimmen' gestures at a remaining-shortfall figure but does not confirm it. It is adequate to attempt a call, but thin for a compute-style tool with no annotated output.

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 all four quantities (required positions, already covered, uniquely matched, multiply/duplicate-matched) are documented in the schema. The description adds no interpretation of how these inputs combine, only restating the overall calculation, so baseline 3 applies.

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 gives a concrete verb pair and resource: fill an existing kitchen-utensil set with actually approved spare parts and determine the remaining shortfall. The 'nur nach Prüfung' framing plus 'tatsächlich freigegebene Ersatzteile' distinguishes it from a plain replacement-matching sibling. What remains fuzzy is the phrase 'Count complete tool capacity', which is a loose gloss rather than a precise statement of the computed result.

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 definition implies the usage condition (only verified/approved substitutes may be counted) but never states when to prefer this tool over the many sibling staging/verification tools. No exclusions, no prerequisites, and no named alternative are given, so an agent must infer selection from the name alone.

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