Skip to main content
Glama

getecoback-raumklima

dunstabzug_geruchsprobe_kueche_nachbarraum_gemeinsame_basis

Read-only

Prüfe, ob eine lokale Geruchsbeobachtung auch im angrenzenden Raum nachgewiesen ist — Compare kitchen and adjacent-room odor observations under matched cooking conditions

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": {
      "kueche_a": "<kueche_a>",
      "nebenraum_a": "<nebenraum_a>",
      "kueche_b": "<kueche_b>",
      "nebenraum_b": "<nebenraum_b>",
      "koch_und_tuerzustand_vergleichbar": "<koch_und_tuerzustand_vergleichbar>"
    },
    "name": "dunstabzug_geruchsprobe_kueche_nachbarraum_gemeinsame_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
kueche_aYesEigene Geruchseinstufung vor Änderung in der Küche, Skala 0 bis 5
kueche_bYesEinstufung am gleichen Küchenort bei der getrennten Nachprobe
nebenraum_aYesZeitgleiche Einstufung am zweiten Ort vor Änderung
nebenraum_bYesZeitgleiche Einstufung am gleichen zweiten Ort bei der Nachprobe
koch_und_tuerzustand_vergleichbarYesGleiche Art der Kochaufgabe, ähnliche Startbedingungen, gleiche Zeitbezüge und Türen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description provides almost nothing behavioral: it does not say what decision rule combines the two paired observations, whether both probes must agree, or what verdict is produced. With no output schema present, that omission leaves the actual behavior opaque.

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 statement is short and front-loaded, leading with the German purpose and following with an English gloss. The bilingual duplication is mildly redundant rather than harmful, and no sentence wanders.

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 read-only, five-parameter comparison with a fully documented schema, the purpose is adequately conveyed. However, a 'Prüfe, ob…' tool lives or dies on its verdict, and with no output schema the description should at least indicate what kind of result (e.g., a yes/no determination or a deviation) comes back, which it does not.

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 five parameters (kueche_a/b, nebenraum_a/b, koch_und_tuerzustand_vergleichbar) are already documented with scale and meaning. The phrase 'matched cooking conditions' loosely echoes the comparability flag but adds no new semantics about scale handling or tolerances. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb ('Prüfe') and a concrete resource (a local odor observation verified in the adjacent room), and the English half clarifies it is a matched-condition kitchen vs. adjacent-room comparison. It is clearly not a plain measurement tool. It stops short of distinguishing itself from the similarly named sibling dunstabzug_geruchsprobe_spitze_dauer_entscheidung, which also deals with odor probes.

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 implied rather than stated: an agent can infer the tool is for verifying whether an odor observed in the kitchen is also detectable next door. There is no explicit when-to-use/when-not-to-use guidance and no reference to any alternative sibling for peak vs. duration questions, so the agent must infer the routing itself.

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