Skip to main content
Glama

getecoback-climate-weather

dunstabzug_licht_probe_kochfeld_ecken_unterschied

Read-only

Prüfe, ob ein eigener Lichtzielwert an beiden Kochfeldpositionen im gleichen Aufbau erreicht wurde — Compare measured illumination at two hood work 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": {
      "de_modell_bestaetigt": "<de_modell_bestaetigt>",
      "vorne_gemessen_lux": "<vorne_gemessen_lux>",
      "hinten_gemessen_lux": "<hinten_gemessen_lux>",
      "eigener_min_lux": "<eigener_min_lux>",
      "beleuchtung_und_sensor_gleich": "<beleuchtung_und_sensor_gleich>"
    },
    "name": "dunstabzug_licht_probe_kochfeld_ecken_unterschied"
  }
}

Input Schema

NameRequiredDescriptionDefault
eigener_min_luxYesSelbst gesetzter Vergleichswert für denselben Arbeitsbereich
vorne_gemessen_luxYesEigene Messung vorne am dokumentierten Arbeitsbereich in Lux
hinten_gemessen_luxYesEigene Messung hinten am dokumentierten Arbeitsbereich in Lux
de_modell_bestaetigtYesDeutscher DWB66BC50 Datenblattbezug bestätigt
beleuchtung_und_sensor_gleichYesSensororientierung, Raumlicht und Haubenlicht für beide Ortsablesungen dokumentiert

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, and the description is consistent with a pure evaluation that mutates nothing. Beyond that, it only adds the same-setup requirement; it does not say what verdict is produced, whether both positions must pass or each is reported separately, or how the self-set target is applied. Useful but thin given the annotations already cover the safety profile.

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 compact sentence with the check condition front-loaded, followed by an English gloss. The bilingual duplication costs a little space but adds no confusion. There is no filler or hedging.

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?

Five required parameters and no output schema mean the description should clarify what the probe returns (pass/fail per position, which side deviates, how a mismatch is flagged). It does not, leaving the result shape entirely unspecified for a read-only check tool. The inputs are well covered by the schema, so the gap is confined to the outcome.

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%, with each of the five parameters individually documented (front/rear lux, own minimum, model confirmation, lighting/sensor parity). The description adds no meaning beyond this, merely restating the two-position comparison. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 gives a specific verb ('Prüfe') plus a concrete comparison resource: whether a self-set target lux value was reached at both cooktop positions in the same setup. That is far more informative than the opaque name. It does not, however, contrast itself with the many sibling dunstabzug probe tools, so an agent must infer the boundary from the position/light framing alone.

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 phrase 'im gleichen Aufbau' implies a precondition (both readings must come from an identical configuration), which is a useful usage constraint. There is no explicit statement of when to prefer this over alternatives such as the shared-basis odour probes, nor any exclusion of cases where the setup differs. Guidance is implied rather than stated.

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