Skip to main content
Glama

getecoback-climate-weather

schallmessung_referenzprobe_vor_nach_drift

Read-only

Prüft ob dieselbe Referenz vor und nach einer Messreihe vergleichbar angezeigt wurde — Check observed meter drift using the same reference before and after a series.

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": "<vorher>",
      "nachher": "<nachher>",
      "toleranz_db": "<toleranz_db>",
      "gleicher_referenzaufbau": "<gleicher_referenzaufbau>"
    },
    "name": "schallmessung_referenzprobe_vor_nach_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorherYesErste Anzeige derselben Referenz in dB.
nachherYesZweite Anzeige derselben Referenz in dB.
toleranz_dbYesZulässiger Abstand der eigenen Vergleichsprobe in dB.
gleicher_referenzaufbauYesGleiche Referenz, Messposition, Instrument und Einstellung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds the concept of drift checking against a reference, but does not say what happens when tolerance is exceeded, how the verdict is reported, or that a non-identical setup changes the result — notably the role of gleicher_referenzaufbau is left implicit.

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 a bilingual restatement) that wastes little space. The German/English duplication is slightly redundant but aids clarity rather than obscuring it.

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?

Inputs are fully specified and the tool is read-only, requiring nothing about permissions. However, with no output schema, the description should explain what result the drift check yields (a pass/fail against toleranz_db, or a computed difference), and it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all four parameters are documented in the schema, so the schema does the heavy lifting. The description contributes only the pairing concept of the two readings, adding little parameter-specific meaning beyond that, which is acceptable given the complete 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 and resource: checking whether the same reference was displayed comparably before and after a measurement series, i.e. observed meter drift. This is clear enough to distinguish it from generic sound measurements, though it does not explicitly contrast with similar siblings such as the A/B or A/C weighting comparisons.

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 'before and after a series' implies the usage context (a paired reference check around a measurement run), but there is no explicit statement of when not to use it or which sibling to prefer for other comparison scenarios.

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