Skip to main content
Glama

getecoback-climate-weather

geraeuschereignis_sel_und_zeitfenster_abgleichen

Read-only

Rechnet ein isoliert gemessenes Ereignis auf zwei unterschiedlich lange Vergleichsfenster um — Convert one isolated event exposure to equivalent levels for two comparison windows.

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": {
      "ereignis_sel": "<ereignis_sel>",
      "fenster_a_sek": "<fenster_a_sek>",
      "fenster_b_sek": "<fenster_b_sek>",
      "ereignis_ganz": "<ereignis_ganz>"
    },
    "name": "geraeuschereignis_sel_und_zeitfenster_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ereignis_selYesGemessener A-bewerteter Ereignispegel SEL mit Bezugsdauer 1 Sekunde in dB.
ereignis_ganzYesEnthalten beide Fenster dasselbe vollständige isolierte Ereignis?
fenster_a_sekYesDauer des Vergleichsfensters A in Sekunden.
fenster_b_sekYesDauer des Vergleichsfensters B in Sekunden.

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 for this pure calculation. The description adds domain semantics (isolated single-event exposure, two windows of differing duration) but does not clarify what happens when ereignis_ganz is false, nor what the result looks like.

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 front-loaded sentence with the operative verb first. The German/English duplication is slightly redundant but compact and adds no filler beyond the translation.

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?

For a simple four-parameter, side-effect-free computation with full schema coverage, the definition conveys enough to call it. The one gap is that no output schema exists and the description only implies the return of two equivalent levels rather than stating the response shape.

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, including ranges and meanings, are fully documented in the schema. The description only echoes the concept of two differently long windows and does not add unit handling or edge-case guidance beyond what the schema already supplies.

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+resource: it converts ('Rechnet ... um') one isolated measured event exposure (SEL) into equivalent levels for two comparison windows of different lengths. The domain action is concrete and distinguishable from neighbours like 'synchron' or 'ueberlappung', though no sibling is named explicitly.

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 guidance, no condition under which this conversion is preferred over alternatives, and no mention of prerequisites such as the requirement that the event be 'isoliert gemessen'. The agent must infer applicability entirely from the domain wording.

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