Skip to main content
Glama

getecoback-climate-weather

klima_geruchsmeldung_raum_und_betriebsphase

Read-only

In einer Geruchsmeldung zwischen Beobachtungen im Raum und an der laufenden Klimaanlage unterscheiden — Use prior on/off observations to prepare a non-diagnostic odour report.

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": {
      "vorher": "<vorher>",
      "waehrend": "<waehrend>",
      "nach_stopp": "<nach_stopp>",
      "raumbedingungen_geaendert": "<raumbedingungen_geaendert>"
    },
    "name": "klima_geruchsmeldung_raum_und_betriebsphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorherYesBeobachtung im Raum vor dem bereits vergangenen Lauf.
waehrendYesBeobachtungsort während des bereits vergangenen Laufs.
nach_stoppYesBeobachtung während einer protokollierten Pause.
raumbedingungen_geaendertYesGab es gleichzeitig eine andere Raumnutzung oder eine geänderte Lüftung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered; the description adds the meaningful constraint that the result is deliberately non-diagnostic, which tells the agent not to over-interpret output. It still says nothing about how the four phase values are combined, what is returned, or validation behaviour for contradictory inputs.

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?

Two short clauses with no filler: the domain framing first, then the usage instruction. The bilingual split is slightly awkward but each half carries distinct information (the German gives the room-vs-unit contrast, the English gives the non-diagnostic constraint), so little is wasted.

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?

All four parameters are required and richly enumerated, and there is no output schema, so the description should explain the report structure or how the phases are evaluated — it does not. For a tool that is effectively a four-value classification input, the definition is adequate but leaves the agent unsure what happens after the call.

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 enums fully specified, so the baseline is 3. The description does add one mapping of value to meaning — 'im Raum' versus 'an der laufenden Klimaanlage' corresponds to the during-run location choice — but it says nothing about 'raumbedingungen_geaendert' or 'nach_stopp' beyond what the schema states.

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 description does convey a resource (an odour report / Geruchsmeldung) and an action (distinguishing room observations from observations at the running AC unit), but the verb is abstract ('unterscheiden') and it never says what the tool actually produces or records. An agent can guess this is a classification/structuring step in an odour complaint workflow, but the phrase 'non-diagnostic odour report' is the only hint at the outcome.

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?

'Use prior on/off observations' implies the tool is invoked when a before/during/after comparison is available, and 'non-diagnostic' implies it should not be used to conclude a root cause. However, no explicit when-not condition or named alternative from the sibling set is given, so selection still requires inference.

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