Skip to main content
Glama

getecoback-raumklima

geraeuschlog_messbereich_gueltige_stichproben

Read-only

Bilanziert ein Geräuschprotokoll mit abgeschnittenen, untersteuernden und fehlenden Messwerten — Count usable readings after excluding clipped, under-range and missing samples.

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": {
      "gesamt": "<gesamt>",
      "oben": "<oben>",
      "unten": "<unten>",
      "fehlend": "<fehlend>"
    },
    "name": "geraeuschlog_messbereich_gueltige_stichproben"
  }
}

Input Schema

NameRequiredDescriptionDefault
obenYesMarkierte Übersteuerungen.
untenYesMarkierte Unterschreitungen des dokumentierten Messbereichs.
gesamtYesErwartete Stichproben im Beobachtungsblock.
fehlendYesFehlende Stichproben ohne Wert.

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 safety is covered. The description adds the useful filtering rule (exclude clipped, under-range and missing samples), but says nothing about the response value, rounding, or what happens when the exclusions exceed the total — a realistic edge case given four free counts.

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 sentences with no filler; the German statement and English gloss mirror each other. The bilingual duplication is slightly redundant but serves as a glossary for the exclusion terms rather than padding.

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 four required numeric parameters, no output schema and no annotations covering return semantics, the description should state what the result looks like (a count, presumably a single number) and how impossible inputs are handled. It covers the exclusion logic but leaves the output side underspecified.

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% with clear German labels for gesamt, oben, unten and fehlend, so the baseline is 3. The description implies the arithmetic relationship among the four counts but never spells it out, adding little beyond the schema's own documentation.

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 and resource — counting usable readings in a noise log — and enumerates the three exclusion categories (clipped, under-range, missing), which lets an agent grasp the computation without reading the schema. It falls short of 5 only because it does not distinguish this from any sibling or state the exact output form.

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 guidance on when to use this tool versus alternatives, no prerequisites (e.g., that counts must be tallied beforehand), and no statement of when the tool is not appropriate. Usage must be inferred entirely from the name and parameter labels.

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