Skip to main content
Glama

getecoback-raumklima

kuehlkombi_kgn39vxct_vitafresh_kaltlagerfach_eulabel

Read-only

Ordnet VitaFresh-Werbung und das gesonderte Kaltlagerfach-Feld der deutschen KGN39VXCT dem richtigen Dokument zu — Distinguish a marketed refrigerator drawer from a declared regulatory compartment

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>",
      "beworbene_schublade": "<beworbene_schublade>"
    },
    "name": "kuehlkombi_kgn39vxct_vitafresh_kaltlagerfach_eulabel"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständig gelesene deutsche Modellkennung.
beworbene_schubladeYesDas eingegebene Angebot ordnet die VitaFresh-Schublade ausdrücklich genau diesem Modell zu.

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, covering the safety profile. The description adds the classification distinction but does not describe output document types, error behavior, or any operational constraints beyond what the annotations provide.

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 compact, front-loading the action and then adding a clarifying dash phrase. It contains no obvious filler, though the mixed German/English phrasing is slightly less scannable.

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 two-parameter read-only classification tool, the description gives the core purpose and the key conceptual distinction, while the schema covers inputs. It is still incomplete because it never explains what 'richtigen Dokument' means or what result to expect, and there is no output schema to fill that gap.

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 coverage is 100%, and both enum parameters are fully documented in the schema. The description reinforces the KGN39VXCT model scope and the VitaFresh drawer concept, but it does not add decision rules or meaning beyond the schema, so the baseline of 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 action, 'Ordnet ... zu', and names the resources involved: VitaFresh advertising and the separate Kaltlagerfach field for the German KGN39VXCT. It also articulates the key distinction between a marketed drawer and a declared regulatory compartment, although 'richtigen Dokument' remains vague and no sibling tool is named.

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 description implies when the tool is relevant by saying it distinguishes VitaFresh advertising from a separately declared Kaltlagerfach field. However, it does not explicitly say when to choose it over the sibling Kaltlagerfach or EU-label tools, nor does it state exclusions.

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