Skip to main content
Glama

getecoback-raumklima

ventilator_messmikrofon_direktwind_kontrollprobe

Read-only

Dokumentiert ob eine auffällige Anzeige auch bei geprüfter Windschutzbedingung bestehen blieb — Compare a meter reading with and without a documented microphone wind condition.

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": {
      "naechste_anzeige_db": "<naechste_anzeige_db>",
      "windkontrolle_db": "<windkontrolle_db>",
      "aufbau_abgeglichen": "<aufbau_abgeglichen>"
    },
    "name": "ventilator_messmikrofon_direktwind_kontrollprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
windkontrolle_dbYesWert eines geeigneten dokumentierten Windschutz-Vergleichs in dB.
aufbau_abgeglichenYesPosition, Einstellung und Quelle sind gleich. Die Eignung des Windschutzes für das Messgerät ist dokumentiert.
naechste_anzeige_dbYesAngezeigter Wert in der auffälligen Probe mit direkter Luftbewegung am Sensor in dB.

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 safety profile is covered and the description need only add context. It does add the substantive precondition that the wind protection must be documented and the setup identical ('aufbau_abgeglichen'), but it never says what the tool returns (a verdict on persistence, a delta, or prose), which matters for a documentation-style tool with 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?

A single sentence that front-loads the deciding condition and then restates it in English, so there is minor redundancy from the bilingual repetition but no filler. The em-dash split keeps the operational core first.

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?

For a three-parameter, read-only comparison tool with full schema coverage and annotations carrying the safety profile, the description covers the preconditions well. The remaining gap is the result: with no output schema, the agent cannot tell whether the call yields a persistence verdict, a numeric delta, or a log entry, which is exactly the thing this tool exists to produce.

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%, so all three parameters — the flagged reading, the wind-protected reference value, and the setup-equivalence flag — are already documented in the schema. The description's 'with and without a documented microphone wind condition' merely paraphrases that split without adding units, tolerances, or interpretation rules beyond what the schema supplies.

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 German sentence names a specific operation on a specific resource: documenting whether an anomalous reading ('auffällige Anzeige') persisted under a verified wind-protection condition, and the English clause reduces it to 'Compare a meter reading with and without a documented microphone wind condition.' That is a distinct control-probe scenario, clearly not a duplicate of generic setup or timer siblings, though 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the triggering situation — an abnormal reading has appeared and you need to check whether it survives a documented wind-protection comparison — which effectively tells the agent when this tool applies. It gives no explicit when-not-to-use condition and points to no alternative tool, so it stops short of full 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