Skip to main content
Glama

getecoback-climate-weather

luftreiniger_sensorabstand_nah_und_aufenthalt

Read-only

Vergleicht Partikeländerungen am Gerät und an einem Aufenthaltsort mit einer Kontrollmessung — Compare particle changes near the purifier and at an occupied location after a baseline check.

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": {
      "nah_vorher": "<nah_vorher>",
      "fern_vorher": "<fern_vorher>",
      "nah_nachher": "<nah_nachher>",
      "fern_nachher": "<fern_nachher>",
      "sensoren_kontrollmessung_aehnlich": "<sensoren_kontrollmessung_aehnlich>"
    },
    "name": "luftreiniger_sensorabstand_nah_und_aufenthalt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nah_vorherYesMesswert A am Gerät zu Beginn in µg/m³ der selben PM-Fraktion.
fern_vorherYesMesswert B am Aufenthaltsort zu Beginn desselben Zeitfensters in µg/m³ der selben PM-Fraktion.
nah_nachherYesMesswert A am Gerät zum Ende in µg/m³ der selben PM-Fraktion.
fern_nachherYesMesswert B am Aufenthaltsort zum Ende desselben Zeitfensters in µg/m³ der selben PM-Fraktion.
sensoren_kontrollmessung_aehnlichYesZeigten die beiden Sensoren bei einer Kontrollmessung nebeneinander unter gleichen Bedingungen ähnliche Werte?

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 safety is covered. The description adds that the comparison is contingent on a control measurement between the two sensors, which is real behavioral context beyond the annotations. However, it never says what happens when the control check fails (does the tool refuse, warn, or still return a comparison?), leaving a meaningful behavioral 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?

One compact bilingual sentence that front-loads the core action (comparing particle changes) before the control-measurement condition. The German/English duplication is slightly redundant but functionally serves as a translation aid and no sentence is wasted.

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?

With five required numeric inputs, no output schema, and a read-only compute semantic, the description should indicate what the agent gets back (a delta comparison, a verdict, a ratio?) and how the boolean control flag affects it. It establishes the input story but leaves the result story entirely unspecified, which is a notable gap for a tool with no output schema.

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 every parameter (nah_vorher, fern_vorher, nah_nachher, fern_nachher, sensoren_kontrollmessung_aehnlich) is already documented with units in µg/m³. The description restates the nah/fern mapping and the control-measurement concept but adds no syntax, pairing rules, or time-window constraints beyond what the schema provides, so baseline 3 applies.

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 ("Vergleicht") and two named resources: particle changes at the device (am Gerät) and at an occupied location (Aufenthaltsort), gated by a control measurement. An agent can tell this is a comparison/computation tool, not a data write. It does not explicitly differentiate itself from the many sibling luftreiniger_* tools, keeping it at 4 rather than 5.

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?

The phrase "after a baseline check" hints at a precondition (a control measurement must exist), but there is no explicit statement of when to use this tool versus alternatives, and no exclusions. No sibling tool is named as a fallback, so the agent must infer the usage context from the parameter names alone.

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