Skip to main content
Glama

getecoback-raumklima

spueler_angebot_geraet_nische_verpackung_trennen

Read-only

Aus einem Küchenangebot die Bezüge von Gehäuse-, Einbau- und Liefermaß sauber trennen — Identify which dimensional evidence is missing from a seller’s listing.

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": {
      "geraetemass_vorhanden": "<geraetemass_vorhanden>",
      "nischenmass_vorhanden": "<nischenmass_vorhanden>",
      "liefermass_vorhanden": "<liefermass_vorhanden>",
      "offenes_tuermass_vorhanden": "<offenes_tuermass_vorhanden>",
      "e_nummer_zugeordnet": "<e_nummer_zugeordnet>"
    },
    "name": "spueler_angebot_geraet_nische_verpackung_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
e_nummer_zugeordnetYesSind die Einträge der genauen Gerätevariante und dem konkreten Lieferangebot zugeordnet?
liefermass_vorhandenYesIst das tatsächlich angebotene Verpackungs- oder Liefermaß belegt?
geraetemass_vorhandenYesIst ein eindeutig beschriftetes geschlossenes Gerätemaß vorhanden?
nischenmass_vorhandenYesIst das Einbaumaß eigenständig als Nischenmaß beschriftet?
offenes_tuermass_vorhandenYesIst das Maß mit geöffneter Tür samt Öffnungsstellung ausgewiesen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 framing that the tool classifies evidence into three dimension categories and flags gaps, but it never discloses the crucial behavioral fact that the tool operates purely on five caller-supplied booleans and returns an assessment derived from them rather than reading a document.

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?

A single compact sentence pair with the core action front-loaded before the em-dash clarification. The German/English doubling is mildly redundant rather than wasteful, and no sentence is filler.

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 five required booleans and no output schema, the description carries the burden of explaining what comes back, and it only vaguely implies a gap report without stating its form. It also leaves unaddressed how the caller should establish each boolean (from which observation or sibling tool). Adequate for orientation, insufficient to call confidently.

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 every boolean is already documented in the schema and the baseline is 3. The description does add a mapping between the three named measure types and the corresponding flags, which helps orientation, but it says nothing about the two remaining parameters (offenes Tuermass, e_nummer_zugeordnet) or how to decide a boolean's value.

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 verb and resource: separating the Gehäuse-, Einbau- und Liefermaß references from a kitchen offer, and identifying which dimensional evidence is missing. An agent can grasp that this is a dimensional-evidence audit rather than a measurement or lookup tool. It does not differentiate itself against any of the many sibling spueler_* evidence tools, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Aus einem Küchenangebot' implies the operating context (evaluating a seller's listing), but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the extensive sibling set. Guidance is implied rather than stated.

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