Skip to main content
Glama

getecoback-climate-weather

luftreiniger_partikel_probe

Read-only

Eigenen Partikelmessvergleich mit und ohne Luftreiniger auswerten — Interpret a paired room particle test with matched starting readings.

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": {
      "off_start": "<off_start>",
      "off_end": "<off_end>",
      "on_start": "<on_start>",
      "on_end": "<on_end>",
      "match_tolerance": "<match_tolerance>",
      "comparable": "<comparable>"
    },
    "name": "luftreiniger_partikel_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
on_endYesPM2,5 am Ende derselben Vergleichsperiode mit Gerät in µg/m³.
off_endYesPM2,5 am Ende derselben Vergleichsperiode ohne Gerät in µg/m³.
on_startYesPM2,5 vor der Vergleichsperiode mit Gerät in µg/m³.
off_startYesPM2,5 vor der Vergleichsperiode ohne Gerät in µg/m³.
comparableYesGleicher Sensor, Messort, Zeitraum und vergleichbare Umgebungsbedingungen? Keine zusätzliche Partikelquelle absichtlich erzeugt?
match_toleranceYesVorab gewählte maximal zulässige Abweichung der Startwerte in µg/m³.

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?

Annotations already declare a read-only, closed-world operation, so the description mainly needs to add interpretive context. It does add the pairing constraint, but says nothing about what the evaluation produces, how the match_tolerance and comparable gates affect the result, or what happens when the measurement is not comparable.

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?

It is a single front-loaded sentence, with the German action first and the English gloss immediately after. Nothing is redundant, and the scope constraint appears before any detail.

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 six required numeric and boolean parameters and no output schema, the definition explains the input situation but not the result of the evaluation or how the comparable/mismatch case is handled. It is adequate for identifying the tool, but incomplete for an agent that needs to predict its behavior.

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 coverage is 100% and the schema already explains each PM2.5 reading, the match_tolerance, and the comparable flag in German. The description only gestures at 'matched starting readings' without adding any semantics beyond the schema, so it sits at the baseline.

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 action ('auswerten' / 'Interpret') and a specific resource ('paired room particle test with and without air purifier'), and the 'matched starting readings' clause narrows the scope fruitfully. It is easy to tell apart from filter or CADR siblings, although no sibling is named explicitly.

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?

The phrase 'matched starting readings' implies this is for tests where the start values align, which helps decide when interpretation is valid, but the description never states when not to use the tool or what to do for unpaired or unmatched measurements. Usage has to be inferred.

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