Skip to main content
Glama

getecoback-raumklima

geraeteton_schmalband_spitze_gegen_nachbarbaender

Read-only

Vergleicht eine beobachtete Frequenzspitze mit den beiden angrenzenden gleich breiten Spektralbändern — Compare an observed spectral peak against equally wide adjacent frequency bins.

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": {
      "band_mitte_db": "<band_mitte_db>",
      "band_darunter_db": "<band_darunter_db>",
      "band_darueber_db": "<band_darueber_db>",
      "gleiche_auswertung": "<gleiche_auswertung>"
    },
    "name": "geraeteton_schmalband_spitze_gegen_nachbarbaender"
  }
}

Input Schema

NameRequiredDescriptionDefault
band_mitte_dbYesAnzeigepegel des untersuchten Frequenzbands in dB.
band_darueber_dbYesAnzeigepegel des direkt darüberliegenden Bands in dB.
band_darunter_dbYesAnzeigepegel des direkt darunterliegenden Bands in dB.
gleiche_auswertungYesGleich breite benachbarte Bänder mit derselben Skalierung und demselben Aufnahmeintervall?

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 safety profile is covered and the bar is lower. The description adds that the comparison involves equally wide adjacent bins, but says nothing about what the comparison produces (delta, verdict, flags) or any preconditions on the measurement setup.

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 comparison target stated first; no filler or hedging. The bilingual duplication is slightly redundant but standard for this catalogue and costs little.

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 no output schema, the description would ideally say what the comparison returns or what counts as a peak standing out from its neighbours. All four inputs are fully described, so the gap is limited to the result side, but it is a real gap for a comparison 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 every parameter including the dB ranges and the equal-width/equal-scaling flag is already documented in the schema. The description only restates the equal-width condition in prose and adds no format or range detail beyond it, which matches the baseline 3.

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 names a specific verb (vergleicht/compare) and a concrete resource pair: an observed spectral peak versus the two adjacent equally wide bins. An agent can tell what the tool computes. It does not distinguish itself from the many sibling comparison tools, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling should be used instead. The scenario (a peak that needs checking against neighbours) is only implied by the noun phrase, not framed as guidance.

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