Skip to main content
Glama

getecoback-climate-weather

betriebsgeraeusch_raumwechsel_beleg

Read-only

Bewerten, ob der protokollierte Schalldruck am eigenen Hörplatz überhaupt belegt ist — Scope a sound pressure observation to the documented listening placement.

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": {
      "fundstelle": "<fundstelle>",
      "aufstellung": "<aufstellung>",
      "betriebsphase": "<betriebsphase>"
    },
    "name": "betriebsgeraeusch_raumwechsel_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundstelleYesMessort des Ausgangswerts.
aufstellungYesEntspricht die Aufstellung dem eigenen Szenario?
betriebsphaseYesEntspricht die beobachtete Phase dem gewünschten Betrieb einschließlich Kompressor?

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 annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only evaluation. It adds that the evaluation concerns documented listening placement and logged sound pressure, but it does not explain the evaluation criteria or what kind of result is returned. With annotations 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the evaluation goal. The bilingual phrasing is somewhat redundant, since the English clause largely restates the German scope clause, but it remains compact and readable.

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?

The tool has three required parameters with full schema coverage and basic safety annotations, but no output schema. The description does not explain the return value or how the boolean parameters combine, and it addresses only the listening-placement aspect of the evaluation. It is workable but leaves meaningful gaps for an evidence-evaluation tool.

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 all three parameters are already documented in the input schema. The description reinforces the 'eigener_hoerplatz' focus through 'am eigenen Hörplatz' and 'documented listening placement', but it does not clarify the boolean parameters 'aufstellung' and 'betriebsphase' beyond the schema. The baseline of 3 is appropriate 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 German clause states a specific action and object: evaluate whether the logged sound pressure at one's own listening position is evidenced. The English clause adds that the observation should be scoped to the documented listening placement. It is clear enough, but it does not explicitly distinguish this tool from similarly named 'beleg' siblings.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no alternative tools. At most, the phrase 'Scope a sound pressure observation to the documented listening placement' implies a usage context, but it does not help an agent choose this tool over siblings.

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