Skip to main content
Glama

getecoback-climate-weather

monoblock_kontaktvibration_zu_schallereignissen

Read-only

Trennt Fälle mit gleichzeitig wahrnehmbarer Kontaktvibration von reinen Geräuschbeobachtungen — Separate logged acoustic events with and without observed contact vibration.

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": {
      "schallereignisse": "<schallereignisse>",
      "beide": "<beide>",
      "vibration_nicht_geprueft": "<vibration_nicht_geprueft>"
    },
    "name": "monoblock_kontaktvibration_zu_schallereignissen"
  }
}

Input Schema

NameRequiredDescriptionDefault
beideYesEreignisse mit zeitgleich an einem frei zugänglichen entfernten Punkt beobachteter Vibration.
schallereignisseYesMarkierte Schallereignisse in derselben Beobachtung.
vibration_nicht_geprueftYesSchallereignisse ohne Vibrationserfassung.

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 safety and locality are covered and the bar is lower. The description adds only the conceptual split between vibration-confirmed and pure-noise events; it does not disclose what the tool returns (counts? per-class totals?), how the three input tallies are combined, or any consistency requirement such as both-events being a subset of total events.

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 sentence, front-loaded with the German statement of purpose and followed by an English rendering; there is no filler. The bilingual duplication costs a little length but aids disambiguation for an ambiguous German tool name.

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 tool is computationally simple (three required numeric inputs, no nested objects), and the description conveys the goal. However, with no output schema and no statement of the return value or of the arithmetic relationship among the three counts, an agent cannot predict the result shape, 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 description coverage is 100%, so each of the three numeric parameters is already documented in the schema with min/max bounds and meaning. The description contributes no additional parameter semantics (e.g., how 'beide', 'schallereignisse' and 'vibration_nicht_geprueft' must relate), so the baseline 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 names a concrete operation ('Trennt Fälle ... von reinen Geräuschbeobachtungen' / 'Separate logged acoustic events with and without observed contact vibration'), which tells an agent this is a classification/separation of logged events rather than a measurement or mutation. It is specific about the two classes being separated, though the cryptic tool name means the description alone carries the load, and it never states what the separation produces.

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 when-to-use guidance, no prerequisite or data-condition requirement (e.g., that vibration recording must have occurred), and no reference to any alternative tool for related acoustic-log work, despite many acoustics-adjacent siblings in the catalog. The agent must infer the usage context entirely.

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