Skip to main content
Glama

getecoback-raumklima

lueftung_co2_abklingtest

Read-only

Luftwechsel aus einer gemessenen CO₂-Abklingkurve grob abschätzen — Estimate apparent air changes from measured CO₂ decay and known outdoor background.

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": {
      "start_ppm": "<start_ppm>",
      "ende_ppm": "<ende_ppm>",
      "aussen_ppm": "<aussen_ppm>",
      "minuten": "<minuten>",
      "fehler_je_ppm": "<fehler_je_ppm>",
      "gueltiger_abschnitt": "<gueltiger_abschnitt>"
    },
    "name": "lueftung_co2_abklingtest"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutenYesDauer des unbelegten Messabschnitts in Minuten.
ende_ppmYesSpäterer Innenwert in ppm am selben Messort.
start_ppmYesZu Beginn des Beobachtungszeitraums bereits gemessener Innenwert in ppm.
aussen_ppmYesGemessener ungefähr konstanter Außenwert in ppm.
fehler_je_ppmYesAbsoluter Toleranzbetrag je Messwert laut Sensorunterlagen.
gueltiger_abschnittYesKeine CO₂-Quelle im Zeitraum, ungefähr konstant durchmischter Raum und Lüftungszustand?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 agent knows this is a self-contained, side-effect-free computation on supplied numbers. The description adds the important caveat that results are coarse ('grob'), but says nothing about the calculation model, its accuracy limits, or which input assumptions dominate the estimate.

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?

Two short clauses, German followed by a faithful English rendering, with the core purpose front-loaded and no filler. Nothing could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only six-parameter calculator with full schema coverage and no output schema, the definition covers purpose, input basis and the rough-estimate caveat. The main residual gap is that no output shape or unit (e.g. air changes per hour) is hinted at, but this is minor given the restricted return scope of a computation tool.

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 each of the six parameters carries its own unit, range and meaning, so the schema does the heavy lifting. The description only restates the conceptual inputs (decay curve, outdoor background) without adding format or interaction detail beyond the schema, which matches the baseline for a fully documented 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?

The description pairs a specific verb ('abschätzen' / estimate) with a specific resource ('Luftwechsel' / air changes) and names the input basis (measured CO₂ decay plus known outdoor background). It is clear enough to distinguish this from measurement-logging or device-selection siblings, though it does not explicitly name a neighbouring alternative.

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?

'Aus einer gemessenen CO₂-Abklingkurve' and 'grob abschätzen' imply the preconditions (existing measurements, only a rough estimate is wanted), and the schema's 'gueltiger_abschnitt' encodes the validity constraints. However, there is no explicit statement of when not to use the tool, nor a pointer to an alternative for cases where the measurement section is invalid.

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