Skip to main content
Glama

getecoback-raumklima

kuehlfach_behaeltertausch_gebrauchte_deckelpaare

Read-only

Nur tatsächlich zueinander passende Vorratsdosen und Deckel für die nächste dokumentierte Ablage zählen — Count usable container pairs by observed compatibility families.

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": {
      "dosen_a": "<dosen_a>",
      "deckel_a": "<deckel_a>",
      "dosen_b": "<dosen_b>",
      "deckel_b": "<deckel_b>",
      "brauche_paare": "<brauche_paare>"
    },
    "name": "kuehlfach_behaeltertausch_gebrauchte_deckelpaare"
  }
}

Input Schema

NameRequiredDescriptionDefault
dosen_aYesGeeignete Vorratsdosen mit bestätigtem Anschluss A.
dosen_bYesWeitere Dosen mit anderem, zu A unpassendem Anschluss B.
deckel_aYesPassende brauchbare Deckel A.
deckel_bYesEntsprechend passende, brauchbare Deckel B.
brauche_paareYesVollständige für die nächste Ablage gesuchte Paare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 useful behavioral note that counting is based on compatibility families, but it does not disclose how the five inputs combine into a result, what the return value looks like, or whether brauche_paare caps the count.

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?

It is a single compact sentence with no filler, and the core scoping condition is front-loaded. The bilingual phrasing is slightly dense but does not waste words.

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 5 required numeric parameters, full schema coverage, no output schema, and no annotations explaining computation, the description should clarify what the tool returns and how brauche_paare interacts with the A/B counts. It implies a count but leaves the actual calculation opaque, which is a meaningful gap for correct invocation.

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 the schema already explains each parameter in German. The description's phrase 'observed compatibility families' marginally reinforces the A/B grouping but adds no syntax, relationship, or edge-case meaning beyond the schema.

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 ('Count') and resource ('usable container pairs') and adds the scope 'by observed compatibility families', which tells an agent this is a pair-counting operation rather than a simple sum. It does not name or distinguish any sibling tool, so it falls short of a 5.

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?

The only usage guidance is the implicit filter 'Nur tatsächlich zueinander passende ... zählen' (only count actually matching ones). There is no statement of when to use this tool instead of the many sibling kuehlfach_* tools, nor any exclusion or prerequisite.

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