Skip to main content
Glama

getecoback-raumklima

spueler_frontart_geteilt_oder_einteilig_belege

Read-only

Bei zwei Möbelfrontvarianten die vorhandene Anleitung, Fronteignung und Zubehörzuordnung getrennt prüfen — Compare documentary support for single and split fronts.

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": {
      "e_nummer_sicher": "<e_nummer_sicher>",
      "einteilig_zeichnung": "<einteilig_zeichnung>",
      "einteilig_front": "<einteilig_front>",
      "geteilt_zeichnung": "<geteilt_zeichnung>",
      "geteilt_schiene": "<geteilt_schiene>",
      "geteilt_front": "<geteilt_front>"
    },
    "name": "spueler_frontart_geteilt_oder_einteilig_belege"
  }
}

Input Schema

NameRequiredDescriptionDefault
geteilt_frontYesDie vorhandenen Frontteile sind für die dokumentierte Variante bestätigt.
e_nummer_sicherYesDie vollständige Modellvariante steht auf dem Beleg oder Typenschild.
einteilig_frontYesDie vorhandene Front ist für diese dokumentierte Variante bestätigt.
geteilt_schieneYesDie geforderte Zubehörzuordnung für genau diese geteilte Front ist dokumentiert.
geteilt_zeichnungYesHerstellerzeichnung für die geteilte Variante vorhanden.
einteilig_zeichnungYesHerstellerzeichnung für die einteilige Variante vorhanden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. Beyond that the description only restates the three evidence areas mapped to the parameters; it never says what the tool returns (a verdict? per-variant result?) or what happens when required evidence is missing, which is the core output of a pure evaluation 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 sentences with the scope front-loaded. The German and English versions are largely duplicative, but the total length is small enough that no sentence is a real burden.

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?

For a six-required-parameter evaluation tool with no output schema, the description omits the most important missing piece: what the returned judgement looks like and how the separate per-variant checks combine. Given the absence of any other structured signal about return behaviour, this leaves the definition under-complete for its complexity.

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 six booleans are already documented individually with clearer wording than the description. The description adds only a loose grouping into instruction/front-suitability/accessory categories, which is a marginal gain over the schema baseline.

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 action (prüfen/compare documentary support) and its object (Anleitung, Fronteignung, Zubehörzuordnung for single vs. split fronts), which is specific enough to distinguish it from drawing- or height-related siblings. It stops short of explicitly naming which sibling to use for the neighbouring checks.

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 opening clause 'Bei zwei Möbelfrontvarianten' implies the triggering situation (two front variants in play), but there is no explicit when-to-use/when-not, no prerequisite stated (e.g. that E-Nummer certainty must already hold), and no alternative named.

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