Skip to main content
Glama

getecoback-climate-weather

luftreiniger_schadstoff_zweck

Read-only

Zwischen Partikelfilterung, Geruchsminderung und Frischluftbedarf unterscheiden — Identify whether a room problem involves particles, odor or outdoor air exchange.

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": {
      "concern": "<concern>",
      "carbon": "<carbon>",
      "ongoing_source": "<ongoing_source>"
    },
    "name": "luftreiniger_schadstoff_zweck"
  }
}

Input Schema

NameRequiredDescriptionDefault
carbonYesFür diese Betriebsart ist eine geeignete Aktivkohlestufe dokumentiert?
concernYesBeobachtung im Raum, keine Diagnose.
ongoing_sourceYesDauerhafte Quelle oder fortlaufende Belastung bekannt?

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 and the description only needs to add context. It adds the framing that this is a classification step rather than a measurement, but it does not say what the classification yields, whether it is advisory only, or how ambiguous/unknown cases are handled — and there is no output schema to fill that gap.

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?

Very short and front-loaded: the decision framing comes first, with the enumeration of the three problem types. The German/English duplication is mildly redundant but does not bloat the text or bury the key information.

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?

All three parameters are required and fully documented in the schema, and the tool is read-only, so the essentials are covered. However, with no output schema the description should indicate what the agent receives back from this classification, and that is left unspecified.

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%, so the baseline is 3 and the schema already explains all three inputs. The description does echo three of the concern enum values (particles, odor, outdoor air exchange) but omits moisture and unknown as well as the carbon and ongoing_source inputs, so it adds little beyond the structured fields.

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 specific discriminating task — deciding whether a room problem is about particle filtration, odor reduction, or fresh-air exchange — which is a recognizable triage/resolution step and is conceptually distinct from the sibling tools (filter change, CADR, cost, etc.). It stops short of saying what the tool actually returns once the classification is made, so it is clear but not fully self-locating.

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?

Use is only implied: an agent can infer it is the entry-point classifier for a room complaint, but the description never states when to call it versus the concrete sibling checks (e.g. particle probe, filter due date) or any prerequisites/exclusions. No explicit when-not guidance.

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