Skip to main content
Glama

getecoback-raumklima

heizluefter_aufgabe_sprachpause_und_waerme

Read-only

Für eine Aufgabe getrennt prüfen, wie viel ausreichend warme Zeit wegen gleichzeitig dokumentierter Geräuschstörung ausfiel — Count the heat that remains usable after overlapping conversation disruption.

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": {
      "aufgabe_min": "<aufgabe_min>",
      "passend_warm_min": "<passend_warm_min>",
      "gestoert_min": "<gestoert_min>",
      "warm_und_gestoert_min": "<warm_und_gestoert_min>"
    },
    "name": "heizluefter_aufgabe_sprachpause_und_waerme"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabe_minYesTatsächlich dokumentierte Arbeits- oder Gesprächsminuten.
gestoert_minYesMinuten, in denen ein Gespräch nach eigenem Protokoll akustisch gestört war.
passend_warm_minYesMinuten mit passender persönlicher Wärme.
warm_und_gestoert_minYesGezielt beobachtete gleichzeitige warme und gestörte Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate a read-only, closed-world calculation, and the description adds that the operation accounts for overlapping warm and disturbed periods. However, it does not disclose the exact calculation logic, validation behavior for inconsistent minute values, or the return form.

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 compact and front-loads the task context, with no filler. The German and English statements are slightly duplicative but remain brief and understandable.

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 four-required-parameter calculation with no output schema, the description conveys the intended result but does not explicitly state the return value, its unit, or how overlapping minutes are combined. Inputs are fully documented by the schema, so the remaining gap is mainly output and edge-case semantics.

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 four minute parameters already have documented meanings and bounds. The description reinforces the task/warm/disturbance/overlap concepts but adds no formula, units beyond minutes, or parameter interaction details beyond the 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?

The description states a specific computation: counting usable warm time after overlapping documented conversation disruption, with German wording adding the per-task framing. It is more than a tautology, though it does not explicitly distinguish itself from similar sibling calculations.

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?

Usage is implied: it is appropriate when task, warm, disturbed, and overlap minutes are documented and an overlap-adjusted usable warm duration is needed. There is no explicit when-not guidance and no named alternative or sibling comparison.

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