Skip to main content
Glama

getecoback-climate-weather

schallspitze_fast_slow_zeitgewichtung

Read-only

Vergleicht zwei Angaben zur Spitzenanzeige mit A-Gewichtung und unterschiedlichen Zeitkonstanten — Compare LAFmax and LASmax from the same measurement interval.

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": {
      "lafmax": "<lafmax>",
      "lasmax": "<lasmax>",
      "derselbe_zeitraum": "<derselbe_zeitraum>"
    },
    "name": "schallspitze_fast_slow_zeitgewichtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
lafmaxYesHöchster F-zeitbewerteter A-Pegel (LAFmax) in dB.
lasmaxYesHöchster S-zeitbewerteter A-Pegel (LASmax) in dB.
derselbe_zeitraumYesGleicher Zeitraum, Messpunkt und A-Gewichtung nachweisbar?

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 the meaningful constraint that both values must come from the same measurement interval, but it does not say what the comparison returns, whether a verdict or a delta, or how a false derselbe_zeitraum is handled.

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 compact clauses, German followed by an English gloss, with the core comparison front-loaded. The bilingual duplication is deliberate and aids matching, though it is the only slightly redundant element.

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 three-parameter read-only comparison with no output schema, the description omits what the tool actually produces — a boolean verdict, a numeric difference, or a diagnostic. An agent knows what to pass in but not what comes back, which is the main remaining gap.

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 coverage is 100%, so each parameter (lafmax, lasmax, derselbe_zeitraum) is already fully documented with units and ranges. The description adds only the framing that the two values belong to one interval, which mildly reinforces the derselbe_zeitraum semantics but goes no further than the schema.

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?

States a specific verb (Vergleicht/Compare) and a specific resource pair (LAFmax vs LASmax, A-weighted peak levels with different time constants). The scientific intent — comparing two peak indicators from one measurement — is unmistakable. No sibling is named, so there is no explicit differentiation from other acoustic-comparison tools.

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 implied rather than stated: 'from the same measurement interval' signals the precondition, and the required boolean derselbe_zeitraum reinforces it. There is no explicit statement of when to prefer this over another comparison tool, nor what to do when the same-interval condition fails.

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