Skip to main content
Glama

getecoback-climate-weather

ventilator_schichttermin_ruhe_noch_zu_bestaetigen

Read-only

Eine vermutete Geräuschüberschneidung zwischen zwei vereinbarten Arbeitsplätzen anhand gemeinsam belegter Beobachtung eingrenzen — Distinguish known disturbance from an uncertain observation edge.

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": {
      "lauter_abschnitt_sicher_min": "<lauter_abschnitt_sicher_min>",
      "moegliche_rand_min": "<moegliche_rand_min>",
      "termin_min": "<termin_min>",
      "hoechstens_stoerend_min": "<hoechstens_stoerend_min>"
    },
    "name": "ventilator_schichttermin_ruhe_noch_zu_bestaetigen"
  }
}

Input Schema

NameRequiredDescriptionDefault
termin_minYesGesamtdauer des gemeinsamen Termins.
moegliche_rand_minYesWeitere möglicherweise überlappende Minuten am selben Arbeitsplatz.
hoechstens_stoerend_minYesMaximal vereinbarte störende Minuten, freiwillig festgelegt.
lauter_abschnitt_sicher_minYesSicher im Termin liegende beobachtete laute Minuten am weiter entfernten Arbeitsplatz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false. The description adds the behavioral idea of distinguishing a known disturbance from an uncertain observation edge, but it does not explain the decision logic, assumptions, or what confirmation outcome is produced.

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?

The definition is short and front-loads the scenario before the distinguishing clause. There is no filler, though the abstract bilingual phrasing slightly reduces immediate clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-required-parameter computational or confirmation tool with no output schema. The description does not explain what the tool returns, how the minute values combine, or how to interpret "noch zu bestätigen," leaving important operational context missing.

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 each of the four required minute-based parameters is documented in the schema. The description adds no additional parameter meaning, units, or constraints beyond what the schema already provides, so the baseline of 3 applies.

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 names a verb ("eingrenzen") and a resource ("Geräuschüberschneidung") and frames a workplace-noise scenario. However, the actual operation remains abstract: it is unclear whether this computes a boundary, confirms an overlap, or classifies an observation. The English clause adds little precision and no sibling differentiation.

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?

It implies a situation involving a suspected noise overlap between two agreed workplaces, but gives no explicit when-to-use guidance, prerequisites, or exclusions. With many similar ventilator/noise siblings, the definition does not help an agent choose this tool over alternatives.

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