Skip to main content
Glama

getecoback-raumklima

raumluft_zwei_sensoren_platztausch_probe

Read-only

Vergleicht Messdifferenzen vor und nach dem Tausch zweier PM-Messgeräte — Compare location differences before and after two particle sensors swap positions.

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": {
      "ort_a_geraet_1": "<ort_a_geraet_1>",
      "ort_b_geraet_2": "<ort_b_geraet_2>",
      "ort_a_geraet_2": "<ort_a_geraet_2>",
      "ort_b_geraet_1": "<ort_b_geraet_1>",
      "bedingungen_stabil": "<bedingungen_stabil>"
    },
    "name": "raumluft_zwei_sensoren_platztausch_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ort_a_geraet_1YesOrt A mit Gerät 1 vor dem Platztausch in µg/m³ der selben PM-Fraktion.
ort_a_geraet_2YesOrt A mit Gerät 2 nach dem Platztausch in µg/m³ der selben PM-Fraktion.
ort_b_geraet_1YesOrt B mit Gerät 1 nach dem Platztausch in µg/m³ der selben PM-Fraktion.
ort_b_geraet_2YesOrt B mit Gerät 2 vor dem Platztausch in µg/m³ der selben PM-Fraktion.
bedingungen_stabilYesBlieben Lüftung, Quellen und Betriebsstufe während des Vergleichs ähnlich?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description's comparison framing is consistent with a pure read/analysis operation, so there is no contradiction. It adds the requirement for comparable conditions, which is useful behavioral context, but it never says what the comparison produces (delta values, a verdict, a threshold), which matters given there is no output schema.

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 front-loaded sentence that states the comparison and its temporal dimension immediately. The German/English duplication is slightly redundant but aids disambiguation for a German-named tool, so it mostly earns its place.

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?

Inputs are fully documented in the schema and the read-only safety profile is covered by annotations, but with no output schema the description should say what the agent receives back from the comparison. That is the main missing piece for a computational tool with five required inputs.

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 parameter already documents its location, device, timing and unit (µg/m³, same PM fraction). The description adds no meaning beyond that, so the 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 names a specific verb and resource: it compares measurement differences before and after two PM sensors swap positions. That is far more precise than the cryptic tool name and lets an agent understand the operation without opening the schema. It does not distinguish itself from related particle-measurement siblings, so it falls short of a 5.

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 usage context is implied by 'vor und nach dem Tausch' and reinforced by the required 'bedingungen_stabil' flag, so an agent can infer this is a post-swap plausibility check. However, there is no explicit when-to-use or when-not-to-use guidance and no alternative sibling is named.

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