Skip to main content
Glama

getecoback-raumklima

h2861bp_auszug_gitter_blech_packeinheit

Read-only

Den deutschen Serienlieferumfang nach individuellen Stücken und angenommenen Paaren abgleichen — Audit the exact H 2861 BP receipt without counting one rail as one pair.

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": {
      "exakte_de_variante": "<exakte_de_variante>",
      "vertrag_enthaelt_serienumfang": "<vertrag_enthaelt_serienumfang>",
      "hbb71": "<hbb71>",
      "hubb71": "<hubb71>",
      "rost": "<rost>",
      "flexiclip_paar": "<flexiclip_paar>",
      "gitter_paar": "<gitter_paar>"
    },
    "name": "h2861bp_auszug_gitter_blech_packeinheit"
  }
}

Input Schema

NameRequiredDescriptionDefault
rostYesIst der einzelne Back- und Bratrost als vorhanden bestätigt?
hbb71YesIst das einzelne HBB 71 als vorhanden bestätigt?
hubb71YesIst das einzelne HUBB 71 als vorhanden bestätigt?
gitter_paarYesIst das vollständige separate Aufnahmegitterpaar als vorhanden bestätigt?
flexiclip_paarYesIst das vollständige HFC 70-C Paar als vorhanden bestätigt?
exakte_de_varianteYesBestätigtes H 2861 BP Edelstahl/CleanSteel mit Materialnummer 12144610.
vertrag_enthaelt_serienumfangYesWird der reguläre Lieferumfang für das konkrete Angebot ausdrücklich erwartet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/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 a genuine behavioral warning that the agent would otherwise get wrong — that rails/gitter must be counted as pairs rather than single units — which is exactly the kind of failure mode this reconciliation guards against.

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?

The definition is front-loaded and short, with the German statement followed by an English restatement. The bilingual duplication is mildly redundant but aids comprehension of a cryptic tool name, and no sentence is wasted.

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 seven required parameters, no output schema, and a read-only annotation set, the description gives enough to call the tool but not enough to predict its result: it never states what the audit returns or how partial ('offen') confirmations affect the verdict. Adequate but leaves a real gap for a seven-input reconciliation tool.

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 per-parameter descriptions and enums for five fields, so the schema carries the semantic load. The description's mention of 'individuellen Stücken und angenommenen Paaren' loosely maps to the single-item vs pair parameters but adds no detail on how 'offen' or 'abweichend' should be interpreted.

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 concrete verb ('abgleichen' / audit) and resource ('Serienlieferumfang' of the H 2861 BP receipt), and the clause 'without counting one rail as one pair' pins down the specific comparison the tool performs. It does not, however, distinguish this from the closely named sibling 'h2861bp_plus_hfc_tabellenspalte_und_ebenenbezug', so the agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance and no named alternative among a large sibling catalog. Usage is only implied by the phrase 'Audit the exact H 2861 BP receipt', leaving the agent to guess whether this is the right tool for a general scope-of-delivery check.

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