Skip to main content
Glama

getecoback-raumklima

camper_heckfach_verschlusswechsel_luftsignal_kontrolle

Read-only

Prüfe, ob das Luftbewegungssignal am Heckfach nur bei geöffneter Fachtür erschien und der vorgelagerte Kontrollpunkt stabil blieb — Compare a storage door intervention against a stable cabin airflow control

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": {
      "heck_offen": "<heck_offen>",
      "heck_zu": "<heck_zu>",
      "kontrolle_offen": "<kontrolle_offen>",
      "kontrolle_zu": "<kontrolle_zu>",
      "nur_fachstellung_gewechselt": "<nur_fachstellung_gewechselt>"
    },
    "name": "camper_heckfach_verschlusswechsel_luftsignal_kontrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
heck_zuYesAm selben Heckfach-Messpunkt in der zulässigen geschlossenen Kontrollstellung Bewegung beobachtet
heck_offenYesAm selben Heckfach-Messpunkt bei offener Fachtür Bewegung beobachtet
kontrolle_zuYesZeitgleich mit geschlossenem Fach dort Bewegung beobachtet
kontrolle_offenYesZeitgleich mit offenem Fach im vorgelagerten Wohnbereich Bewegung beobachtet
nur_fachstellung_gewechseltYesÜbrige Aufstellung, Messmethoden und Zeitbedingungen sind dokumentiert vergleichbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 safety is covered and the description's remaining burden is to explain how the five booleans are combined into a verdict. It never states what is returned (a boolean pass/fail? a diagnosis?), what happens when nur_fachstellung_gewechselt is false, or which combination counts as confirmation. For a pure logic-evaluation tool, that omission is exactly the missing behavioral content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence, but the structure is a bilingual duplication: the German clause is precise and the English gloss restates it less accurately, so roughly half the text does not earn its place. Front-loading the check itself is good.

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

Completeness2/5

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

There is no output schema, so the description must explain what a caller gets back from feeding in five booleans — and it does not. Combined with absent usage guidance and no sibling differentiation, an agent can pass the parameters correctly but cannot predict or interpret the result.

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 five booleans carries a precise German definition, so the schema does the heavy lifting. The description adds only a loose framing ('nur bei geöffneter Fachtür', 'Kontrollpunkt stabil blieb') that gesture at the intended truth pattern without adding syntax or interpretation rules beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The German clause names a concrete check: whether the airflow signal at the rear compartment (Heckfach) appeared only with the compartment door open while the upstream control point stayed stable. However, the English gloss ('Compare a storage door intervention against a stable cabin airflow control') is vaguer than the German and adds no precision, and nothing distinguishes this tool from siblings such as camper_heckfach_stichprobe_oeffnung_veraendert. The purpose is inferable but requires domain decoding.

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?

No indication of when to use this instead of the other camper_heckfach or airflow-signal tools, no prerequisite conditions, and no exclusion criteria. The only implicit cue is that it expects four already-observed boolean readings plus a comparability flag.

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