Skip to main content
Glama

getecoback-raumklima

luftreiniger_hepa_werbeaussage_pruefen

Read-only

HEPA-Angaben zum Filter vom Nachweis am ganzen Luftreiniger trennen — Distinguish a filter class declaration from tested whole-device performance.

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": {
      "beleg": "<beleg>",
      "variante": "<variante>",
      "gesamttest": "<gesamttest>"
    },
    "name": "luftreiniger_hepa_werbeaussage_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegYesVorliegender Beleg.
varianteYesTrifft die genannte Filterklasse auf das genaue Einsatzmodell zu?
gesamttestYesExistiert zusätzlich ein Geräteprüfbericht mit Prüfmethode und Betriebsstufe?

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 safety is covered. The description adds the conceptual distinction the tool performs but says nothing about what the result looks like or how the three inputs combine into a verdict, which is the main behavioral unknown for a reasoning/check tool.

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?

A single compact sentence pair, front-loaded with the core distinction. The German and English restate the same content, which costs a little space but usefully disambiguates terminology.

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 three-parameter, read-only judgment tool with full schema coverage and no output schema, the description is adequate but thin: it does not state what conclusion or categories the agent should expect, nor how conflicting inputs (e.g. filterklasse_mit_pruefnorm but gesamttest=false) are treated.

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 three parameters documented and an enum on 'beleg', so the schema carries parameter meaning. The description does not elaborate on how 'variante' and 'gesamttest' interact with the enum value, leaving no added semantics beyond the schema.

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 analytical task: separating a filter-class declaration from tested whole-device performance. A verb is only implicit ('trennen'/distinguish), and no sibling (e.g. luftreiniger_cadr_raumcheck) is named as an alternative, so it stops short of a 5.

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 the framing 'HEPA-Angaben zum Filter vom Nachweis am ganzen Luftreiniger trennen', which tells the agent this applies to advertising/nachweis situations. There is no explicit when-to-use, when-not-to-use, or pointer to a related tool for adjacent questions such as CADR or filter replacement.

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