Skip to main content
Glama

getecoback-raumklima

geraeuschdaten_leisewert_modusabdeckung

Read-only

Prüft ob der leiseste Datenblattwert den tatsächlich geplanten Gerätebetrieb dokumentiert — Check whether a published minimum noise figure represents the intended mode.

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": {
      "zielmodus": "<zielmodus>",
      "belegmodus": "<belegmodus>",
      "nur_werbezahl": "<nur_werbezahl>"
    },
    "name": "geraeuschdaten_leisewert_modusabdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielmodusYesGesuchter Betrieb.
belegmodusYesFür den veröffentlichten Mindestpegel genannter Betrieb.
nur_werbezahlYesLiegt die Zahl ausschließlich ohne Geräte- oder Messkontext vor?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations align with a pure verification check, and the description confirms it performs an assessment rather than a mutation. It does not say what a verdict looks like, whether a partial match is possible, or how ambiguous datasheet values are handled, so it adds only modest context beyond the annotations.

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 claim, front-loaded with the check itself. The full German/English repetition is redundant for an agent but does not obscure meaning.

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 three-parameter read-only check with no output schema, the description explains the question being answered but not the shape of the answer or what counts as documentation versus misattribution. Enough to select the tool, not enough to interpret or act on its result confidently.

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 both enums are self-explanatory, so the schema already carries the parameter meaning. The description's phrasing ("leisester Datenblattwert" / "geplanter Gerätebetrieb") loosely maps to belegmodus and zielmodus but adds no new detail, such as how "nicht_genannt" or nur_werbezahl affect the verdict.

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 specific verb ("Prüft"/"Check whether") and a concrete comparison: whether a published minimum noise figure reflects the intended device mode. It is clear what the tool decides, though the German/English duplication repeats the same statement rather than narrowing it further.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this check versus other noise or datasheet tools, no prerequisites, and no exclusions. The only hint is the topic itself, leaving the agent to infer applicability.

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