Skip to main content
Glama

getecoback-climate-weather

geraeuschmessung_mikrofon_abschattung_paar

Read-only

Erfasst, ob Abschattung durch die beobachtende Person die Pegelprobe am selben Messpunkt verändert — Check how the observer position changes a fixed-point level reading.

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": {
      "ohne_abschattung": "<ohne_abschattung>",
      "mit_abschattung": "<mit_abschattung>",
      "modus_gleich": "<modus_gleich>",
      "aufloesung_db": "<aufloesung_db>"
    },
    "name": "geraeuschmessung_mikrofon_abschattung_paar"
  }
}

Input Schema

NameRequiredDescriptionDefault
modus_gleichYesGleicher Messpunkt, Gerätemodus, Hintergrund und Messintervall?
aufloesung_dbYesUnterscheidungsbreite der eigenen Anzeige oder Messreihe in dB.
mit_abschattungYesMesswert mit Person zwischen Gerät und Mikrofon in dB.
ohne_abschattungYesMesswert ohne Person zwischen Gerät und Mikrofon in dB.

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?

The annotations already establish this is a safe, closed-world read operation, so the description's burden is lowered. It contributes the paired-comparison framing (a reading with versus without a person between device and microphone), but it never says what the tool returns, whether a verdict or threshold is applied, or what happens if modus_gleich is false. With a read-only annotation covering the safety profile, this is adequate rather than rich.

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?

The text is short but partly redundant because it contains a German sentence followed by an English near-paraphrase that is actually vaguer than the original ('Check how the observer position changes a fixed-point level reading' loses the 'Abschattung' shadowing concept). The core statement is front-loaded, but the second clause does not fully earn its place.

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 four-parameter, fully described, read-only comparison tool with no output schema, the description covers what is compared but says nothing about the result or the precondition that all four inputs describe one consistent measurement setup. This is minimally sufficient rather than complete.

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%: all four parameters carry descriptions plus min and max bounds, so the schema does the documentation work. The description reinforces that both readings must be at the same measurement point, which relates to modus_gleich, but adds no units, units semantics, or handling details beyond the schema. Baseline 3 is appropriate.

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?

A specific verb is combined with a specific resource: 'Erfasst, ob Abschattung durch die beobachtende Person die Pegelprobe am selben Messpunkt verändert' tells an agent this is a paired A/B level-comparison for observer shadowing. It does not differentiate itself from the many sibling measurement tools by name or scope, but on its own its purpose is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites (for example that both readings must come from the same device mode and interval), and no named alternatives. The scenario is only implied by the phrase 'am selben Messpunkt'.

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