Skip to main content
Glama

getecoback-climate-weather

raumluft_geruch_und_co2_getrennt_beobachten

Read-only

Hält die empfundene Geruchsänderung und die gleichzeitig gemessene CO₂-Änderung getrennt fest — Record perceived odour and measured CO₂ changes separately.

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": {
      "geruch_veraendert": "<geruch_veraendert>",
      "co2_vor_ppm": "<co2_vor_ppm>",
      "co2_nach_ppm": "<co2_nach_ppm>",
      "co2_messung_vergleichbar": "<co2_messung_vergleichbar>"
    },
    "name": "raumluft_geruch_und_co2_getrennt_beobachten"
  }
}

Input Schema

NameRequiredDescriptionDefault
co2_vor_ppmYesCO₂-Sensor vor dem Versuch in ppm.
co2_nach_ppmYesCO₂-Sensor nach dem Versuch in ppm.
geruch_veraendertYesSubjektiver Geruchseindruck am selben Standort.
co2_messung_vergleichbarYesWurden mit demselben CO₂-Sensor am selben Standort vergleichbare Messungen vorgenommen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/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 should then add behaviour such as what the result conveys (e.g. whether the two changes are judged consistent or contradictory) or how co2_messung_vergleichbar=false affects the conclusion. It adds nothing here beyond the conceptual framing of keeping the signals apart. The verb 'festhalten'/'Record' also reads faintly like persistence, which sits uneasily with readOnlyHint=true, though the tool name 'beobachten' (observe) points to the read-only reading.

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?

Each language version is a single tight sentence with the core action front-loaded and no filler. The full German/English duplication doubles the length, which is mildly wasteful, though it is plausibly deliberate for a bilingual household-experiment toolset.

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?

Four required scalar parameters, all fully documented in the schema, no output schema, and a read-only annotation set make this a simple tool that needs little prose. What is missing is the outcome semantics (what the tool reports when odour and CO2 move in different directions) and the boundary against sibling odour/CO2 tools, so it is adequate but not complete.

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%, including the enum values and ppm ranges, so the schema carries parameter meaning and a baseline of 3 applies. The description reinforces the intended divide between the subjective odour parameter and the measured ppm parameters but adds no format, ordering, or validity detail beyond that.

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 the specific action (keeping odour change and CO2 change separately) and adds a real qualifier beyond the tool name: 'empfundene' (perceived/subjective) odour versus 'gemessene' (measured) CO2, which tells an agent the tool juxtaposes a subjective and an objective signal. It does not, however, contrast itself with plausibly related siblings such as the odour-narrowing or CO2-decay tools, so an agent must still infer the boundary.

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 when-to-use statement, no prerequisite (e.g. that a before/after CO2 reading must exist), and no named alternative for related odour or CO2 scenarios. The only hint is the word 'getrennt', which implies not conflating the two signals, but this is a methodological aside rather than routing guidance.

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