Skip to main content
Glama

getecoback-climate-weather

fensterabdichtung_randgeraeusch_quellenvergleich

Read-only

Vergleicht den gemessenen Unterschied zwischen zwei Randpunkten vor und nach einem Kitwechsel — Compare changes in a measured noise-level difference between two seal edges.

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": {
      "vorher_a_db": "<vorher_a_db>",
      "vorher_b_db": "<vorher_b_db>",
      "nachher_a_db": "<nachher_a_db>",
      "nachher_b_db": "<nachher_b_db>",
      "quelle_gleich": "<quelle_gleich>"
    },
    "name": "fensterabdichtung_randgeraeusch_quellenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_a_dbYesPegel an Rand A vor dem Wechsel in dB(A).
vorher_b_dbYesPegel an Rand B vor dem Wechsel in dB(A).
nachher_a_dbYesPegel an Rand A nach dem Wechsel in dB(A).
nachher_b_dbYesPegel an Rand B nach dem Wechsel in dB(A).
quelle_gleichYesVergleichbare Quelle, Fensterstellung, Messdistanz und Messdauer?

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 the safety profile is covered and the bar is lower. The description adds that the operation is a comparison of a difference before and after a seal swap, which conveys the conceptual computation, but it does not state the output form, the sign/ordering convention of the delta, or what happens when quelle_gleich is false.

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 bilingual sentence with the concept front-loaded and no filler. The German/English duplication is redundant but short enough not to be wasteful.

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-parameter computation with no output schema and no annotations beyond read-only, the definition should say what is returned and how the quelle_gleich precondition affects the result. It conveys the intent but leaves the return value and the gating behavior unspecified.

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 including the dB ranges and the quelle_gleich gate are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description states a specific verb (vergleicht/compare) and a concrete object (the measured difference between two seal edges before and after a kit change), so an agent understands this is a before/after differential computation rather than a raw measurement. It does not explicitly contrast itself with adjacent tools such as the tape-surface temperature or length tools, so it falls 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only hint of applicability is the quelle_gleich gate, but the description never says how a false value should be handled (refusal, warning, or degraded result), leaving the agent to guess.

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