Skip to main content
Glama

getecoback-raumklima

pinguino_ex105_fensterkit_angebotsumfang

Read-only

Trenne beim PAC EX105 den Geräte-Lieferumfang von einer zusätzlich angebotenen Fensterabdichtung — Verify whether a PAC EX105 offer adds the required window seal

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": {
      "modell_ex105": "<modell_ex105>",
      "bietet_fensterabdichtung": "<bietet_fensterabdichtung>",
      "vorhandener_fenstertyp": "<vorhandener_fenstertyp>",
      "kit_fenstertyp": "<kit_fenstertyp>"
    },
    "name": "pinguino_ex105_fensterkit_angebotsumfang"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_ex105YesVollständige Modellbezeichnung PAC EX105 im Angebot bestätigt
kit_fenstertypYesVom Zubehörhersteller für das enthaltene Set benannte Bauart
vorhandener_fenstertypYesFensterbauart am vorgesehenen Platz
bietet_fensterabdichtungYesDer Händler nennt ausdrücklich eine Fensterabdichtung im Paket

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and nothing in the description contradicts that. The description adds the useful framing that this is a two-sided comparison (device scope vs. add-on seal), but it never says what the verdict looks like or how an 'offen' value is treated, which matters because there is no output schema.

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 description is short and front-loads the core operation before the verification goal. The German and English sentences largely restate each other, which costs a small amount of redundancy, but there is no filler beyond that.

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?

For a read-only classification tool with four fully documented enum parameters and no output schema, the description covers the input scenario adequately. It is silent on the result shape and on how conflicting values (e.g., seal claimed but window type incompatible) are resolved, which is a real gap for an evaluation 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 all four parameters enum-typed and documented in German, so the schema carries the parameter semantics. The description does not clarify the distinction between kit_fenstertyp and vorhandener_fenstertyp or how mismatches are judged, so it adds little beyond the schema; 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 states a specific verb and object: separating the PAC EX105 device scope of delivery from an optionally offered window seal, and verifying whether the offer adds the required seal. It is a clear, narrow purpose, but it never names or contrasts a sibling tool, so differentiation is left to inference.

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?

Usage is implied by 'beim PAC EX105' and 'einer zusätzlich angebotenen Fensterabdichtung', which scopes the tool to PAC EX105 offer checks. There is no explicit when-not guidance and no alternative named for related offer-comparison tasks, so the agent must infer the routing itself.

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