Skip to main content
Glama

getecoback-raumklima

camper_heckfach_stichprobe_oeffnung_veraendert

Read-only

Erkenne, ob nach dem Öffnen eines Staufachs nur dessen eigener Feuchtewert oder gleichzeitig der Wohnbereich wechselte — Compare the storage reading shift with the living-area reference after opening

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": {
      "fach_vor_rh": "<fach_vor_rh>",
      "fach_nach_rh": "<fach_nach_rh>",
      "gang_vor_rh": "<gang_vor_rh>",
      "gang_nach_rh": "<gang_nach_rh>",
      "toleranz_pp": "<toleranz_pp>",
      "temperaturbedingungen_passend": "<temperaturbedingungen_passend>"
    },
    "name": "camper_heckfach_stichprobe_oeffnung_veraendert"
  }
}

Input Schema

NameRequiredDescriptionDefault
fach_vor_rhYesIm geschlossenen Fach erfasste relative Feuchte vor Öffnung
gang_vor_rhYesZeitgleicher früherer Wert im Wohnbereich
toleranz_ppYesEigene gemeinsame Toleranz des Feuchtevergleichs in Prozentpunkten
fach_nach_rhYesSpäterer Wert desselben Sensors im Fach
gang_nach_rhYesZeitgleicher späterer Wert im Wohnbereich
temperaturbedingungen_passendYesTemperaturen je Messpaar und Reaktionszeiten ausreichend ä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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe pure-computation profile is covered. The description does add the underlying decision logic (compartment shift vs. living-area shift), but it never states what the result looks like, how the tolerance value gates the verdict, or what happens when the temperature conditions are unsuitable.

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?

The definition is two short clauses with the core condition front-loaded and the English half serving as a terse restatement. The bilingual duplication is mildly redundant but costs little and aids comprehension.

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?

With six required parameters, a boolean gating flag, and no output schema, the description should say more about the verdict it produces and the role of the tolerance and temperature checks. It conveys the comparison concept adequately but leaves the agent guessing about the result shape.

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 six parameters are already documented in the schema, including the mapping of 'fach' to compartment and 'gang' to living area. The description reinforces the two-sided comparison conceptually but adds no syntax, units, or tolerance-application detail beyond the schema; 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 states a specific detection task: determine whether opening a storage compartment changed only that compartment's own humidity reading or also the living-area reference. That is a clear verb-plus-resource framing (a differential comparison), though it never names a sibling or explicitly marks its boundary against the many other camper sampling tools.

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?

Usage is only implied by the phrase 'nach dem Öffnen' (after opening) and by the mention of a living-area reference. There is no explicit when-to-use or when-not-to-use statement, and no guidance on prerequisites such as the temperature-suitability gate being satisfied before the comparison is meaningful.

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