Skip to main content
Glama

getecoback-raumklima

schallmessung_a_c_gewichtung_gleichzeitige_spreizung

Read-only

Berechnet den Unterschied zeitgleich gemessener C- und A-gewichteter Mittelwerte — Calculate the simultaneous LCeq minus LAeq difference.

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": {
      "lceq_db": "<lceq_db>",
      "laeq_db": "<laeq_db>",
      "gleichzeitige_messung": "<gleichzeitige_messung>"
    },
    "name": "schallmessung_a_c_gewichtung_gleichzeitige_spreizung"
  }
}

Input Schema

NameRequiredDescriptionDefault
laeq_dbYesSelbst gemessener A-gewichteter äquivalenter Pegel LAeq in dB.
lceq_dbYesSelbst gemessener C-gewichteter äquivalenter Pegel LCeq in dB.
gleichzeitige_messungYesGleicher Zeitraum, Messort und vergleichbare Instrumenteneinstellung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 clear. The description adds the core calculation behavior, namely subtracting LAeq from LCeq, but does not discuss validation, error behavior, or output characteristics beyond the implied difference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact clauses with the calculation front-loaded and no redundant wording. The bilingual phrasing adds accessibility without wasting space.

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 three-parameter calculation with complete schema coverage and no output schema, the definition gives enough context to invoke it correctly. It could explicitly state the expected return value in dB or clarify any measurement preconditions, but the core operation is sufficiently 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%, and the schema already explains LAeq, LCeq, and the simultaneity check in detail. The description reinforces that these are simultaneous C- and A-weighted means, but adds no parameter meaning beyond what the schema provides.

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 difference between simultaneously measured C-weighted and A-weighted mean levels, and gives the formula LCeq minus LAeq. This is clear and concrete, but it does not explicitly differentiate itself from sibling measurement tools or name an alternative.

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 'zeitgleich gemessener' and the required 'gleichzeitige_messung' boolean imply that the tool applies when C- and A-weighted measurements come from the same period and setup. However, the description does not explicitly say when to use this tool versus related sibling calculations or what conditions would make it inappropriate.

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