Skip to main content
Glama

getecoback-raumklima

geraeusch_aufstellung_rueckkehrtest_a_b_a

Read-only

Vergleicht zwei Platzierungen mithilfe einer wiederholten Ausgangsmessung am selben Hörplatz — Compare placement B against before-and-after readings at placement A.

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_vorher_db": "<a_vorher_db>",
      "b_db": "<b_db>",
      "a_nachher_db": "<a_nachher_db>",
      "eigene_toleranz_db": "<eigene_toleranz_db>",
      "versuch_vergleichbar": "<versuch_vergleichbar>"
    },
    "name": "geraeusch_aufstellung_rueckkehrtest_a_b_a"
  }
}

Input Schema

NameRequiredDescriptionDefault
b_dbYesMessung an Aufstellung B in dB.
a_vorher_dbYesErste Vergleichsmessung an Aufstellung A in dB.
a_nachher_dbYesKontrollmessung nach regulärer Rückkehr zu Aufstellung A in dB.
eigene_toleranz_dbYesEigener maximal zulässiger Unterschied der A-Kontrollen in dB.
versuch_vergleichbarYesGleiche Gerätestufe, Hörposition, Untergrundbedingungen der jeweiligen Aufstellung und Messdauer?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the meaningful methodological point that the A readings form a repeated baseline used to validate placement B, but it does not say what happens when eigene_toleranz_db is exceeded or whether a verdict is returned. With annotations carrying the safety burden, this is an adequate but not rich disclosure.

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 clauses, front-loaded with the core purpose, with effectively no waste. The bilingual restatement is slight redundancy but aids clarity rather than obscuring it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter read-only comparison tool with no output schema, the description conveys the measurement design needed to call it correctly. The main remaining gap is what the comparison yields (pass/fail versus delta), which an agent might want to know before invoking it.

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 each parameter is already documented in the schema, including the role of the two A readings and the comparability boolean. The description confirms the before/after framing but adds no syntax, unit, or interpretation detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific action (comparing two placements) and the method (repeated baseline readings at placement A), which is distinctive from sibling measurement tools such as raumtuer_schallmessung_a_b. It does not explicitly say how it differs from those siblings, so it falls 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?

The A-B-A structure implies the usage context — you need a trustworthy baseline before judging placement B — but there is no explicit when-to-use statement, no exclusion of alternatives, and no mention of when this method is inappropriate (e.g. no comparable baseline). Usage is inferable rather than stated.

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