Skip to main content
Glama

getecoback-raumklima

kuehlkombi_kgn39vxct_led_effizienzklasse_geraet

Read-only

Ordnet C und G im deutschen Bosch-Datenblatt dem Kühlschrank oder seiner LED-Lichtquelle zu — Separate appliance and light-source efficiency ratings in an exact fiche

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>",
      "feld": "<feld>"
    },
    "name": "kuehlkombi_kgn39vxct_led_effizienzklasse_geraet"
  }
}

Input Schema

NameRequiredDescriptionDefault
feldYesZu klärende Zeile des Produktdatenblatts.
modellYesModellkennung aus dem vorliegenden deutschen Angebot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 substantive behavior (which class maps to which entity), but says nothing about the response shape, about out-of-scope model handling, or whether an ambiguous fiche yields a partial answer.

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

Conciseness3/5

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

It is short and front-loaded, but the German sentence and the English dash clause largely duplicate each other ('Ordnet C und G ... zu' / 'Separate appliance and light-source efficiency ratings'), so half the text does not earn its place. The trailing 'in an exact fiche' is vague 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?

For a two-parameter read-only lookup with no output schema, the description conveys the task adequately. What is missing is any statement of the expected result (a mapping verdict?) and how non-matching models are handled, which matters because 'anderes_modell' and 'offen' are valid inputs.

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% and both parameters carry enum values with descriptions, so the schema already does the explanatory work. The description reinforces that 'feld' concerns a specific datasheet line and that C/G assignment is the subject, but adds no new meaning beyond the enumerated options.

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 operation (assigning efficiency classes C and G from a German Bosch datasheet to either the refrigerator unit or its LED light source), which is a specific verb+resource rather than a restatement of the tool name. It does not explicitly contrast itself with nearby siblings such as led_eu_label_lichtquelle_umgebendes_produkt, so differentiation is inferred rather than stated.

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: use this when a datasheet shows two efficiency classes and their attribution is ambiguous. There is no explicit when-not guidance, no mention of what to do with 'anderes_modell' or 'offen', and no named alternative tool for the general case.

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