Skip to main content
Glama

getecoback-raumklima

kuehlschrank_luftschallemissionsklasse_db_schwellen

Read-only

Überprüft A bis D für EU-Kühlschrank-Luftschallemissionen und unterscheidet das besondere geräuscharme Kühlgerät — Read the noise class and special low-noise definition from the correct sound-power value

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": {
      "wert_dba": "<wert_dba>",
      "wertbezug": "<wertbezug>",
      "dampfkompression": "<dampfkompression>"
    },
    "name": "kuehlschrank_luftschallemissionsklasse_db_schwellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_dbaYesDeklarierter Schallwert des Modells, falls bekannt.
wertbezugYesBezugsgröße des angegebenen Werts.
dampfkompressionYesDampfkompression ist für das exakt zugeordnete Gerät dokumentiert oder ausdrücklich ausgeschlossen.

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 meaningful behavioral point that classification depends on the value being a correct sound-power figure, but never states what the tool returns or does when wertbezug is 'schalldruck_im_raum' or 'offen'.

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?

Two compact sentences with the classification scope front-loaded, and the second clause narrows to the special low-noise case. The German/English duplication repeats the same content rather than adding new information, costing a little efficiency.

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?

It is a read-only lookup with a fully documented three-parameter schema and no output schema, so the description's statement of what is read (class plus special low-noise definition) is roughly sufficient. The gap is that a required applicability parameter (dampfkompression) and the unspecified-value cases are not addressed, leaving an agent unsure how decisive each input is.

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%, so each parameter is already documented in the schema; baseline is 3. The description reinforces that wertbezug must be a sound-power reference, which adds modest semantic weight, but it never mentions the required 'dampfkompression' parameter even though that field governs whether the EU noise classification applies at all.

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?

Names a specific check (A–D noise class for EU refrigerator airborne emissions) plus a second outcome (identifying the special low-noise appliance), so the resource and verb are unambiguous. It stops short of naming or contrasting any sibling tool, but the scope is narrow enough that confusion is unlikely.

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 'from the correct sound-power value' implies a precondition (the declared value must be referenced to sound power), which is a usable hint. However, there is no explicit when-to-use guidance, no statement of what to do when the reference basis is sound pressure or 'offen', and no named alternative.

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