Skip to main content
Glama

getecoback-climate-weather

ventilator_schwenkung_spitzenabschnitte_am_platz

Read-only

Ordnet beobachtete Pegelspitzen am Sitzplatz zwei Phasen derselben Schwenkbewegung zu — Summarize observed noise peaks during and outside a fan pass.

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": {
      "passagen": "<passagen>",
      "spitzen_passagen": "<spitzen_passagen>",
      "restbloecke": "<restbloecke>",
      "spitzen_rest": "<spitzen_rest>",
      "zeiten_gleich": "<zeiten_gleich>"
    },
    "name": "ventilator_schwenkung_spitzenabschnitte_am_platz"
  }
}

Input Schema

NameRequiredDescriptionDefault
passagenYesVollständig dokumentierte Vorbeipassagen.
restbloeckeYesGleich lang protokollierte Abschnitte außerhalb der Passage.
spitzen_restYesEreignisse in diesen übrigen Abschnitten.
zeiten_gleichYesSind Passagen und Restabschnitte tatsächlich gleich lang und identisch ausgewertet?
spitzen_passagenYesEreignisse während solcher Passagen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 peaks are partitioned into two phases of one oscillation movement, which is real behavioral context, but says nothing about what the summarization returns, how the zeiten_gleich guard affects the result, or any failure behavior.

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?

Two short clauses, front-loaded with the core operation and no filler. The bilingual duplication of the same idea costs a little space but does aid comprehension of the 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?

It is a read-only computation over five fully documented inputs, and no output schema exists, so the description should at minimum characterize the result (a count comparison? a ratio? a verdict?). That characterization is missing, leaving the return value undefined.

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 all five parameters carry German descriptions, so the schema does the heavy lifting and a baseline 3 applies. The description adds no meaning beyond the schema, such as how passagen and restbloecke are expected to relate or what happens when zeiten_gleich is false.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb+object ('Ordnet beobachtete Pegelspitzen ... zwei Phasen ... zu' / 'Summarize observed noise peaks'), so the general operation is graspable. But the two halves disagree in emphasis (assign-to-phases vs. summarize) and neither names what distinguishes this tool from siblings like ventilator_schwenkbereich_sitzplaetze or ventilator_messmikrofon_direktwind_kontrollprobe.

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?

'during and outside a fan pass' hints at a comparative use case, but there is no explicit statement of when to call this versus the many other ventilator_* tools, and no prerequisites or exclusions. An agent must infer the scenario 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