Skip to main content
Glama

getecoback-climate-weather

schallquelle_hintergrundspanne_schaetzintervall

Read-only

Gibt ein Modellintervall für den Quellenanteil bei variierendem dokumentiertem Hintergrund an — Bound an independent source contribution using a measured background range.

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_db": "<gesamt_db>",
      "hintergrund_min_db": "<hintergrund_min_db>",
      "hintergrund_max_db": "<hintergrund_max_db>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "schallquelle_hintergrundspanne_schaetzintervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_dbYesGesamtpegel am Messort als LAeq in dB.
vergleichbarYesGerät und Hintergrund als unabhängig und Messbedingungen vergleichbar dokumentiert?
hintergrund_max_dbYesOberer LAeq des Hintergrunds in dB.
hintergrund_min_dbYesUnterer LAeq des am selben Ort separat gemessenen Hintergrunds in dB.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context by framing the result as a model/bound ('Modellintervall', 'Bound') rather than a measurement, but it is silent on what happens when 'vergleichbar' is false and on whether the bound is one- or two-sided.

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?

It is a single compact sentence with a parallel English restatement, front-loading the outcome ('Modellintervall für den Quellenanteil'). The bilingual duplication is mild redundancy but aids disambiguation and costs little space.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it only names it ('Modellintervall') without stating its shape or units. Combined with the unexplained consequence of 'vergleichbar' being false, the definition is adequate but leaves real gaps for a four-parameter computation 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 all four parameters are already documented with units (LAeq in dB) and bounds, which sets the baseline at 3. The description only adds the framing that the min/max background values constitute a varying range and that independence is the criterion behind 'vergleichbar' — a marginal addition rather than new syntax or semantics.

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 gives a specific verb and output ('Gibt ein Modellintervall ... an') plus the resource it concerns ('Quellenanteil bei variierendem dokumentiertem Hintergrund'), and the English gloss reinforces it. It is identifiable as a computation tool distinct from the other listed siblings, but the key term 'Quellenanteil'/'source contribution' is left undefined, so the purpose is clear only at a technical level.

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: the phrase 'bei variierendem dokumentiertem Hintergrund' and 'independent source contribution' suggest it applies when the background is documented as a range and is independent of the source. There is no explicit when-to-use, when-not-to-use, or named alternative, and the gating effect of 'vergleichbar' is never spelled out.

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