Skip to main content
Glama

getecoback-raumklima

lueftungsversuch_aussen_delta_raumhintergrund

Read-only

Vergleicht PM-Änderungen innen und außen während desselben beobachteten Öffnungsversuchs — Compare matched indoor and outdoor particle changes during a window-opening observation.

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": {
      "innen_start": "<innen_start>",
      "innen_ende": "<innen_ende>",
      "aussen_start": "<aussen_start>",
      "aussen_ende": "<aussen_ende>",
      "instrumente_abgeglichen": "<instrumente_abgeglichen>"
    },
    "name": "lueftungsversuch_aussen_delta_raumhintergrund"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_endeYesInnenmesswert zum Ende in µg/m³ der selben PM-Fraktion.
aussen_endeYesAußenmesswert zum selben Ende in µg/m³ der selben PM-Fraktion.
innen_startYesInnenmesswert zum Start in µg/m³ der selben PM-Fraktion.
aussen_startYesAußenmesswert zum selben Start in µg/m³ der selben PM-Fraktion.
instrumente_abgeglichenYesWurden PM-Fraktion, Uhrzeiten und Vergleichbarkeit der Sensoren geprüft?

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 by structured data. The description adds the matching requirement, but leaves open what happens when `instrumente_abgeglichen` is false (rejection vs. warning) and what the comparison produces. Useful but thin context beyond annotations.

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?

A single front-loaded sentence with the operative constraint stated before the English mirror. The bilingual duplication adds length but no ambiguity; nothing is padded.

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?

Five required parameters and no output schema mean the description should indicate what the comparison returns (a delta, a ratio, a verdict on whether opening succeeded). That is missing, though the input side is fully covered by the 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% and every parameter carries a units-and-fraction note, so the baseline of 3 applies. The description reinforces the matched-pair semantics of the four numeric inputs but adds no format, ordering, or tolerance guidance beyond the schema.

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?

States a specific verb ("Vergleicht") and a specific resource (matched indoor/outdoor PM changes during one window-opening observation). The pairing constraint ("während desselben beobachteten Öffnungsversuchs") distinguishes it from a generic delta or weather-pair tool, though it does not name a sibling to route away from.

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 implied by the phrase "während desselben beobachteten Öffnungsversuchs" — you must have start/end values from one matched observation. There is no explicit statement of when to prefer this over the sibling `lueftungsversuch_wetterpaare_eignung` or any precondition failure mode.

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