Skip to main content
Glama

getecoback-climate-weather

luftwaescher_partikelnachweis_unterlage

Read-only

Prüfe die Art des Partikelnachweises hinter dem Begriff Luftwäscher — Check the type of particulate evidence behind an air washer claim

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": {
      "werbebegriff": "<werbebegriff>",
      "belegart": "<belegart>",
      "gleiches_modell_und_betrieb": "<gleiches_modell_und_betrieb>"
    },
    "name": "luftwaescher_partikelnachweis_unterlage"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegartYesHerstellerunterlage für Partikelreinigung
werbebegriffYesWas steht auf der Werbung?
gleiches_modell_und_betriebYesPartikelwert dem Modell und vorgesehenen Betriebsmodus zugeordnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world check. The description adds the domain framing that the check concerns evidence behind a claim, but it does not describe the result, classification criteria, or any limitations 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.

Conciseness5/5

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

The description is a single front-loaded statement with no filler, duplicated only as a German-English pair for a German-domain tool. Every sentence earns its place.

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-required-parameter classification tool with no output schema, the definition states what is checked but not what the check returns or how the enum values combine into a conclusion. It is minimally adequate but leaves meaningful gaps about the result.

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 each parameter has an enum or boolean description explaining its meaning. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 gives a specific verb and object: checking the type of particulate evidence behind an air washer claim. It is clear what the tool examines, though it does not distinguish itself from any sibling tool.

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 only implied: an agent can infer this applies when auditing a 'Luftwäscher' advertising claim. There is no explicit when-to-use guidance, no exclusions, and no named alternative among the many sibling tools.

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