Skip to main content
Glama

getecoback-raumklima

schallmessung_zwei_aufstellungen_eigener_hintergrund

Read-only

Vergleicht zwei Aufstellungen, nachdem für jede der separat gemessene eigene Hintergrund berücksichtigt wurde — Compare two placements using their own measured background levels.

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_gesamt_db": "<a_gesamt_db>",
      "a_basis_db": "<a_basis_db>",
      "b_gesamt_db": "<b_gesamt_db>",
      "b_basis_db": "<b_basis_db>",
      "getrennte_belege": "<getrennte_belege>"
    },
    "name": "schallmessung_zwei_aufstellungen_eigener_hintergrund"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_basis_dbYesHintergrund-LAeq A ohne dieses Gerät in dB.
b_basis_dbYesHintergrund-LAeq B ohne dieses Gerät in dB.
a_gesamt_dbYesGesamt-LAeq A mit laufendem Gerät in dB.
b_gesamt_dbYesGesamt-LAeq B mit laufendem Gerät in dB.
getrennte_belegeYesStabile unabhängige Hintergründe und gleiche Messmethode am selben Hörplatz?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, self-contained computation. The description adds the meaningful behavioral point that a background correction is applied per placement, but it says nothing about what the comparison produces, how large a correction is tolerated, or what happens when the 'getrennte_belege' precondition is false.

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, front-loaded operation statement followed by a bilingual restatement — efficient overall, though the German/English duplication is pure redundancy for an agent that reads either language.

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?

With five required numeric/boolean parameters and no output schema, the definition should say what the result looks like (a corrected difference, a verdict, both) and how the boolean gate affects the outcome. It covers the input semantics adequately but leaves the return and failure behavior underspecified.

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 coverage is 100%, so every parameter including the 'getrennte_belege' validity check is already documented in the schema. The description only echoes the background/measurement distinction without adding format, tolerance, or interpretation guidance, 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 and operation: it compares two placements after subtracting each one's separately measured background level. The object ('Aufstellungen' — placements of what device/room) is left implicit, and it does not distinguish itself from the many sibling sound-measurement tools, 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 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 guidance, no exclusions, and no named alternative among the numerous sibling measurement tools. The only hint is the embedded precondition that each background must have been measured separately, which is stated as part of the operation rather than as usage advice.

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