Skip to main content
Glama

getecoback-raumklima

ventilator_nacht_geraeuschprofil_kompromiss

Read-only

Zwei beobachtete Lüfterstufen für die Nacht anhand eigener Luftstrom- und Geräuschgrenzen filtern — Find which measured fan settings meet independently chosen air speed and sound criteria.

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": {
      "a_luft_m_s": "<a_luft_m_s>",
      "b_luft_m_s": "<b_luft_m_s>",
      "a_dba": "<a_dba>",
      "b_dba": "<b_dba>",
      "mindestens_luft_m_s": "<mindestens_luft_m_s>",
      "hoechstens_dba": "<hoechstens_dba>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "ventilator_nacht_geraeuschprofil_kompromiss"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dbaYesA-bewerteter Pegel am Liegeplatz bei Stufe A.
b_dbaYesA-bewerteter Pegel am Liegeplatz bei Stufe B.
a_luft_m_sYesLuftgeschwindigkeit beim Liegeplatz in Stufe A.
b_luft_m_sYesLuftgeschwindigkeit beim selben Liegeplatz in Stufe B.
vergleichbarYesGleicher Messort und ähnliche Raum- und Hintergrundbedingungen?
hoechstens_dbaYesSelbst gewählte obere Geräuschmarke.
mindestens_luft_m_sYesSelbst gewählter Mindestluftstrom beim Liegeplatz.

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 safety profile is covered. The description adds that the thresholds are "independently chosen" (i.e. supplied by the caller, not derived), but says nothing about what happens when the levels are not comparable or what the result looks like.

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 sentences with the core action front-loaded and no filler. The German and English halves are largely duplicative, which costs a little density but aids clarity.

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 seven required parameters are documented and the operation is read-only, but with no output schema the description never explains what the filter returns (a boolean, the surviving level, a recommendation), which is the main thing an agent still needs to know.

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 seven parameters are already documented in the schema. The description only restates the two conceptual inputs (air speed and sound criteria) without adding format, units, or interaction details beyond the schema, so the 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?

States a specific verb ("filtern") and resource ("Zwei beobachtete Lüfterstufen für die Nacht") plus the criteria used, so an agent knows this is a two-level pass/fail comparison rather than a measurement or control tool. It does not name a sibling to contrast with, so it stops short of a 5.

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: the tool applies when two measured night levels exist and the user has chosen their own airflow/sound limits. There is no explicit when-not guidance and no pointer to alternatives such as the level-selection or night-mix siblings, leaving the agent to infer routing.

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