Skip to main content
Glama

getecoback-climate-weather

lueftung_schallpfad_fassadenbeleg_oder_anlagengeraeusch

Read-only

Ordnet beim Lüftungsvergleich Geräusche von außen, vom Luftdurchlass und aus dem Gerätebereich getrennt ein — Identify which observed paths have evidence for exterior, terminal or equipment noise.

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": {
      "aussen": "<aussen>",
      "durchlass": "<durchlass>",
      "geraet": "<geraet>"
    },
    "name": "lueftung_schallpfad_fassadenbeleg_oder_anlagengeraeusch"
  }
}

Input Schema

NameRequiredDescriptionDefault
aussenYesBefund zur Außenquelle im eigenen Protokoll.
geraetYesGeräusch am Gerätebereich.
durchlassYesGeräusch an Luftdurchlass in dokumentierter Betriebsstufe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 contributes the behavioral point that the three noise sources are assessed separately ('getrennt') and that the task is about evidence for observed paths, but it says nothing about the outcome shape or what 'offen' implies for downstream handling.

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?

Two short, front-loaded clauses with no filler, but the English sentence is a straight restatement of the German one rather than new information, so half the text is redundant for a single-purpose definition.

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 small read-only tool with three fully documented required enums and no output schema, the definition covers the essentials. It is still thin on what the classification result means (no output schema exists to compensate) and gives no tie-in to the sibling comparison workflow.

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 all three parameters are enums with documented values, so the schema carries the param semantics. The description only echoes the three sources (exterior, terminal, equipment) that map one-to-one to the parameters, adding no syntax or interpretation guidance beyond that.

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 German sentence gives a specific verb ('Ordnet ... getrennt ein' / 'Identify') plus resources (Geräusche von außen, Luftdurchlass, Gerätebereich), and the English gloss restates it as identifying which paths have evidence. It is clear what the tool produces — a per-path evidence classification — though it never differentiates itself from the many sibling 'lueftung_*' 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 context is implied by 'beim Lüftungsvergleich' (during a ventilation comparison) and by 'observed paths', which suggests it applies to already-recorded observations. There is no explicit when-not guidance, no prerequisites, and no pointer to an alternative sibling tool for adjacent tasks.

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