Skip to main content
Glama

getecoback-climate-weather

schallreport_gesamtwert_teilstichproben_widerspruch

Read-only

Prüft einen berichteten Gesamtmittelwert gegen die Spanne vollständiger Teilmittelwerte — Check a reported equivalent sound level against the range of complete subinterval means.

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>",
      "teil_min": "<teil_min>",
      "teil_max": "<teil_max>",
      "rundungsspiel": "<rundungsspiel>",
      "gleiche_basis": "<gleiche_basis>"
    },
    "name": "schallreport_gesamtwert_teilstichproben_widerspruch"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtYesVeröffentlichter LAeq des Gesamtintervalls in dB.
teil_maxYesHöchster LAeq der Teilintervalle in dB.
teil_minYesNiedrigster LAeq der vollständigen Teilintervalle in dB.
gleiche_basisYesDecken die Teilintervalle denselben Gesamtzeitraum vollständig ab und haben Gewichtung und Messpunkt überein?
rundungsspielYesZulässiges Rundungsspiel aus der Anzeige in dB.

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 agent knows this is a closed-domain, side-effect-free check. The description adds the conceptual model (compare reported mean against the envelope of complete subinterval means) but never says what the tool emits on success versus a detected inconsistency, and there is no output schema to fill that gap.

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 bilingual sentence with the comparison target front-loaded and no filler. The German/English duplication costs some length, but it earns its place by making the domain term 'Teilmittelwerte' unambiguous for non-German readers.

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?

Five required numeric/boolean parameters and no output schema mean the description should ideally indicate the verdict format (contradiction detected or not) and how rundungsspiel and gleiche_basis affect the outcome. It covers the inputs conceptually but leaves the return value and the tolerance logic unexplained.

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%: all five parameters carry German descriptions including units (dB), bounds, and the meaning of gleiche_basis and rundungsspiel. The description restates the roles of gesamt and teil_min/teil_max but adds no semantics beyond the schema, so the baseline of 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 names a specific verb (prüft/check) and a specific comparison: a reported overall LAeq versus the range spanned by complete subinterval means. That is far more precise than the tautological tool name and lets an agent recognize it as a consistency/plausibility check. It stops short of distinguishing itself from the many other '*_widerspruch' siblings in the catalog.

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 when-to-use or when-not guidance, no mention of the alternative consistency-check tools, and no stated prerequisites such as needing a complete, same-basis subinterval set. The comparison described implies the scenario, but the agent must infer the trigger condition entirely from the name and purpose.

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