Skip to main content
Glama

getecoback-raumklima

geraeuschaufnahme_pegel_von_wiedergabe_trennen

Read-only

Entscheidet anhand der Aufnahmekette, ob Tondateien für einen Pegelvergleich geeignet sind — Check whether recorded gain and reference settings support a level comparison.

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": {
      "regelung": "<regelung>",
      "nachtraeglich_normalisiert": "<nachtraeglich_normalisiert>",
      "gemeinsamer_bezug": "<gemeinsamer_bezug>"
    },
    "name": "geraeuschaufnahme_pegel_von_wiedergabe_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
regelungYesBelegte Aufnahmeverarbeitung.
gemeinsamer_bezugYesGleiche Aufnahmekette und dokumentierter gemeinsamer Pegelbezug?
nachtraeglich_normalisiertYesWurde mindestens eine Datei nachträglich normalisiert oder komprimiert?

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 and the description is consistent with it. The description adds that the verdict is derived from the recording chain, but does not say what form the answer takes (boolean, verdict, or explanation) or what happens downstream when files are unsuitable. Given annotation coverage, a middle score is appropriate.

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 sentence with the decision criterion stated first, followed by the English rendering. No padding or filler. The bilingual duplication is slightly redundant but aids matching the German tool name to its English 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 small read-only, three-parameter check the description covers the essential 'what', and the annotations cover safety. With no output schema, however, the agent gets no hint about the shape of the verdict or what distinguishes a passing from a failing recording chain, which is the core value of this tool. Adequate but with a real gap.

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 all three parameters carry their own descriptions plus an enum for 'regelung'. The description's phrase 'recorded gain and reference settings' loosely maps onto 'regelung' and 'gemeinsamer_bezug' but adds no interpretation rules, e.g. how 'unklar' or 'automatik' affects the verdict. Baseline 3 is correct 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?

The description states a specific function: it decides based on the recording chain whether audio files are suitable for a level comparison. That is a clear verb ('decides/checks') plus a clear condition, and no sibling in the list covers this audio-gain concern. It stops short of 5 because the German name ('separate recording level from playback') suggests a separation/orientation task, while the description frames it purely as a suitability check — an agent must reconcile the two.

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 agent can infer the tool belongs upstream of a level comparison, which is useful context. There is no explicit when-to-use, when-not-to-use, or named alternative for cases the check rejects. Nothing misleading, but the routing guidance is left to inference.

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