Skip to main content
Glama

getecoback-climate-weather

geraeuschbericht_dezibel_ausgabeform_zeitprofil

Read-only

Entscheide, ob ein veröffentlichtes Geräuschprofil die gesuchte ruhige Zeit überhaupt abdeckt — Verify silent-window coverage in a documented noise profile

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": {
      "messdauer_min": "<messdauer_min>",
      "ruhige_min": "<ruhige_min>",
      "ziel_min": "<ziel_min>",
      "ausgabeart": "<ausgabeart>",
      "gleiche_messbasis": "<gleiche_messbasis>"
    },
    "name": "geraeuschbericht_dezibel_ausgabeform_zeitprofil"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_minYesGewünschte Dauer unter dem gewählten Vergleichswert
ausgabeartYesDarstellung, der die ruhige Zeit entnommen wurde
ruhige_minYesDarin für denselben Messort ununterbrochen unter dem Vergleichswert dokumentierte Minuten
messdauer_minYesDauer des ausgewerteten Schallprotokolls in Minuten
gleiche_messbasisYesGleiche Pegelgröße, Messposition und gewünschte Gerätephase dokumentiert

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 safety and locality are covered. The description adds that this is a pass/fail coverage decision over documented data rather than a measurement, which is useful. But with no output schema it never states what the decision returns (e.g. a boolean, a shortfall amount, or the reason for non-coverage), leaving the result form ambiguous.

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 clauses, front-loaded with the decision verb, with no filler. The German and English halves are near-duplicates rather than complementary, which is mild waste but aids disambiguation across languages.

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?

For a five-required-parameter read-only check with full schema coverage, most invocation needs are met. However, with no output schema the description should ideally specify what the verdict looks like and how a documented profile that is too short is reported, and it does not.

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 five parameters are already documented, including the enum for ausgabeart and the 0-1440 bounds. The description only loosely maps its vocabulary onto the inputs ("gesuchte ruhige Zeit" to ruhige_min/ziel_min, "veröffentlichtes Profil" to messdauer_min), adding no new constraint or interpretation beyond the schema. 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?

Both language halves state a specific action and object: "Entscheide, ob ein veröffentlichtes Geräuschprofil die gesuchte ruhige Zeit überhaupt abdeckt" / "Verify silent-window coverage in a documented noise profile." This is a coverage/decision check rather than a computation, and the scoping words "veröffentlicht" and "dokumentiert" make the resource type clear. It does not contrast itself with any sibling, so it stops 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 Guidelines3/5

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

"überhaupt abdeckt" / "Verify ... at all" implies the tool is for the pre-check question of whether a documented profile is even usable before deeper analysis. No when-not condition, no prerequisites, and no alternative tool is named, so usage is only implied rather than stated.

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