Skip to main content
Glama

getecoback-climate-weather

geraeuschprobe_grundpegel_rueckkehr_nach_ereignis

Read-only

Beurteilt ob der gemessene Grundpegel nach einem Ereignis wieder im eigenen Ausgangsband lag — Assess whether the measured post-event background returned to its initial band.

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": {
      "vor_db": "<vor_db>",
      "nach_db": "<nach_db>",
      "band_db": "<band_db>",
      "gleicher_modus": "<gleicher_modus>"
    },
    "name": "geraeuschprobe_grundpegel_rueckkehr_nach_ereignis"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_dbYesZeitmittel vor dem beobachteten Geräusch in dB.
band_dbYesEigenes Toleranzband um die Ausgangsanzeige in dB.
nach_dbYesZeitmittel nach Ende des Geräuschs in dB.
gleicher_modusYesGleicher Betriebszustand, Messort und Auswertungsdauer der Grundphasen?

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?

The readOnlyHint and openWorldHint=false annotations already establish this as a safe, closed-world computation, so the description's burden is lighter. It adds the key behavioral framing that the verdict is a comparison against the initial band, but says nothing about how the verdict is produced (thresholds, what happens when gleicher_modus is false, or what the answer looks like). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is short and front-loaded, but the German sentence and the English sentence convey the same content, effectively doubling the length without adding information. It is not padded with fluff, yet half the text is redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four fully documented required parameters and readOnly annotations, the definition covers everything needed to invoke the tool correctly. The one gap is that it never indicates the nature of the result (presumably a boolean verdict plus comparison), which matters for a judgment tool with no output schema, though this is a minor omission given the explicit name.

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 four parameters are already documented in the schema with units and ranges. The description adds only the high-level relationship among them (post-event level versus initial band), not unit, format, or edge-case semantics beyond what the schema provides. Baseline 3 applies.

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 verb and object: it judges ('Beurteilt') whether the measured post-event background level returned to its own initial band. An agent can tell this is an evaluative/comparison tool rather than a measurement or logging tool. It does not, however, distinguish itself from the many similarly named 'Rueckkehr nach ...' siblings, so sibling differentiation is left to the name alone.

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 by the parameter set: you supply a pre-event mean, a post-event mean, a tolerance band, and a flag for identical operating conditions. There is no explicit statement of when to call this instead of a sibling such as a return-after-pause check, and no stated preconditions or exclusions.

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