Skip to main content
Glama

getecoback-raumklima

klima_geraeuschmeldung_ausschnitt_abdeckung

Read-only

Vorhandenen Geräuschausschnitt auf Grundbetrieb, Ereignis und Rückkehr prüfen — Check whether an existing clip contains the noise transition and context.

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": {
      "aufnahme_s": "<aufnahme_s>",
      "geraeusch_start_s": "<geraeusch_start_s>",
      "geraeusch_ende_s": "<geraeusch_ende_s>",
      "ende_tatsaechlich_erfasst": "<ende_tatsaechlich_erfasst>"
    },
    "name": "klima_geraeuschmeldung_ausschnitt_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufnahme_sYesLänge der vorhandenen Aufnahme in Sekunden.
geraeusch_ende_sYesBeobachtetes oder letztes sichtbares Geräuschende in Sekunden.
geraeusch_start_sYesErster beobachteter Geräuschbeginn in der Aufnahme.
ende_tatsaechlich_erfasstYesEnde gehört bzw. im Verlauf tatsächlich festgehalten?

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 and the description only needs to add context. It does add the three coverage criteria (base operation, event, return), but it never states the form of the verdict or what counts as adequate coverage.

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 check stated first and the criteria after the dash. The German/English duplication adds length but also makes the intent unambiguous for either language, so it is only mildly wasteful.

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?

No output schema exists, so the description would need to say what the check returns (a boolean, a gap list, a verdict) and how the four required inputs combine into that result. It covers the input side adequately but leaves the result side entirely implicit, which is a real gap for the agent's next decision.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented, and this is a no-nesting, no-enum simple schema. The description reinforces the temporal span being checked (start/end of the noise versus the recording) without contradicting the schema, so it sits just above the mandated baseline.

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 ('prüfen/check') and resource ('vorhandenen Geräuschausschnitt') and narrows the question to whether the clip contains the noise transition plus context. It is clear on its own, but it never names or distinguishes itself from any sibling coverage-check tool.

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: an agent can infer it applies when a recording already exists and coverage must be verified. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as an evaluation or measurement tool among the many klima 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