Skip to main content
Glama

getecoback-climate-weather

kuehlkombi_kgn39vxct_winterschaltung_belegt

Read-only

Prüft, ob eine angebotene Bosch KGN39VXCT für unbeheizte Räume eine ausgewiesene Winterschaltung hat — Verify the named fridge-freezer winter-setting claim against its German EU sheet

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": "<modell>",
      "angeboten": "<angeboten>"
    },
    "name": "kuehlkombi_kgn39vxct_winterschaltung_belegt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Modellkennung laut dem konkret ausgewählten deutschen Angebot.
angebotenYesWird die Winterschaltung im vorliegenden Angebot ausdrücklich behauptet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 useful behavioral context by identifying the German EU sheet as the verification basis, but it does not explain the result format, what happens for 'anderes_modell' or 'offen', or how evidence is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single, front-loaded sentence with no wasted wording. The bilingual German/English phrasing is compact and directly useful for a German-market tool without becoming repetitive.

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?

The tool is simple with two required enum parameters and full schema coverage, and annotations cover its read-only nature. However, because there is no output schema, the description should explain what a verification returns—an assessment, evidence, or boolean—and it does not, leaving a meaningful gap for an agent invoking it.

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 both parameters and their enums are already documented. The description reinforces that 'angeboten' concerns an offered unit and a claim, but it does not add syntax or enum-level meaning beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Prüft, ob ... eine ausgewiesene Winterschaltung hat' / 'Verify the ... winter-setting claim against its German EU sheet.' It names the exact model (KGN39VXCT) and the precise attribute being checked, which distinguishes it from sibling tools about cooling circuits, LED efficiency, or VitaFresh compartments.

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 purpose implies when the tool is useful—checking a winter-setting claim for an offered KGN39VXCT—but it does not explicitly say when to use this versus alternatives, nor does it name any sibling or exclusion condition. Guidance is therefore 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