Skip to main content
Glama

getecoback-climate-weather

luftreiniger_partikelverlauf_nach_abschalten

Read-only

Vergleicht den Partikelmesswert beim Abschalten und nach einer festgehaltenen Wartezeit — Measure particle reading rebound after a purifier is switched off.

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": {
      "beim_abschalten": "<beim_abschalten>",
      "nachher": "<nachher>",
      "abstand_min": "<abstand_min>",
      "quelle_geaendert": "<quelle_geaendert>"
    },
    "name": "luftreiniger_partikelverlauf_nach_abschalten"
  }
}

Input Schema

NameRequiredDescriptionDefault
nachherYesSpäterer Messwert in µg/m³ der selben PM-Fraktion.
abstand_minYesWartezeit zwischen den Messungen in Minuten.
beim_abschaltenYesMesswert an derselben Stelle beim Abschalten in µg/m³ der selben PM-Fraktion.
quelle_geaendertYesKam eine erkennbare Partikelquelle hinzu oder fiel eine Quelle weg?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 useful detail that the comparison spans a fixed waiting window, but with no output schema it should also say what the call yields (delta, ratio, verdict) and how quelle_geaendert affects the interpretation; neither is disclosed.

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 short clauses, front-loaded with the core comparison and the operational context; nothing is padded. The German/English duplication costs a little length but makes the intent unambiguous for mixed-language agents.

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 four-required-parameter comparison tool with no output schema, the definition should clarify what the computed result represents. It covers the input scenario well enough to invoke the tool but leaves the agent guessing about the return value and how a flagged source change alters the conclusion.

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. The phrase 'festgehaltenen Wartezeit' loosely echoes abstand_min but adds no new syntax or constraint, and the description never explains the interpretive role of quelle_geaendert beyond what the schema already states.

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 operation (comparing two particle readings) and the scenario (switch-off plus a fixed waiting period), so an agent can tell it is a before/after rebound check rather than a single-sample read. It does not distinguish itself from the close sibling luftreiniger_partikel_probe, which is the main missing differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The description implies the tool is for post-switch-off scenarios but never says what to do when a confounding source appeared or disappeared, which is exactly the situation the quelle_geaendert parameter exists to flag.

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