Skip to main content
Glama

getecoback-climate-weather

geraeuschphase_eigenes_mittel_verfuegbare_zeit

Read-only

Errechnet den maximalen Anteil eines lauteren Abschnitts für ein selbst gewähltes Zeitmittel — Solve for the time allowance of a louder phase under a chosen equivalent level.

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": {
      "ruhiger_db": "<ruhiger_db>",
      "lauter_db": "<lauter_db>",
      "ziel_db": "<ziel_db>",
      "gesamt_sek": "<gesamt_sek>",
      "messbasis_gleich": "<messbasis_gleich>"
    },
    "name": "geraeuschphase_eigenes_mittel_verfuegbare_zeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_dbYesEigenes LAeq-Vergleichsziel in dB.
lauter_dbYesLAeq der lauteren Phase in dB.
gesamt_sekYesGesamtdauer des reinen Zwei-Phasen-Szenarios in Sekunden.
ruhiger_dbYesLAeq der leiseren Vergleichsphase in dB.
messbasis_gleichYesGleicher Messort und gleiche Gewichtung für beide Zustände?

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?

The annotations already declare that this is a read-only, closed-world operation. The description adds the conceptual behavior of solving for an allowable louder-phase share, but it does not disclose the result's unit, edge-case behavior, or what assumptions the calculation makes beyond the input schema.

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?

The definition is a single, front-loaded sentence with little wasted wording. The German/English duplication is somewhat redundant, but it does not obscure the core computation.

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?

The input schema is fully described, but there is no output schema and the description does not state whether the result is a fraction, percentage, or seconds. For a calculation tool where the returned time allowance is the key outcome, this is a notable gap, though the core input contract remains clear.

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 already have documented meanings and ranges. The description does not add parameter-specific semantics beyond what the schema provides, making the baseline score appropriate.

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 computation: the maximum share or time allowance of a louder phase under a chosen equivalent level. It uses a clear verb ('Errechnet'/'Solve for') and identifies the computed quantity, but it does not explicitly distinguish this tool from related sibling calculations such as klimageraet_schallzeit_mittel_zwei_phasen.

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?

The phrase 'für ein selbst gewähltes Zeitmittel' and 'under a chosen equivalent level' implies the scenario in which the tool applies. However, it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance, so the agent must infer the selection context.

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