Skip to main content
Glama

getecoback-climate-weather

punktwaerme_aufgabenzeit_ausfallursachen

Read-only

Die dokumentierte Arbeitszeit ohne gewünschte Punktwärme nach Vorlauf, Platzwechsel und offenem Rest aufteilen — Account for distinct sources of missing comfort during an attended task.

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_min": "<passend_min>",
      "zu_frueh_am_platz_min": "<zu_frueh_am_platz_min>",
      "platzferne_min": "<platzferne_min>"
    },
    "name": "punktwaerme_aufgabenzeit_ausfallursachen"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabe_minYesTatsächlich beaufsichtigte Arbeitsminuten.
passend_minYesDavon Minuten mit bestätigter Wärme an deinem tatsächlichen Platz.
platzferne_minYesWeitere Minuten ohne gewünschte Wärme außerhalb des beobachteten Wärmebereichs.
zu_frueh_am_platz_minYesMinuten ohne gewünschte Wärme vor dem ersten Erreichen, bereits anwesend.

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 safety is covered and the bar is lower. The description adds that the split is over documented time into three named sources, which is genuine behavioral context, but it omits the arithmetic relationship (e.g. that the open remainder is derived from the other three inputs) and gives no hint about what the result contains.

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?

It is a single compact statement with the core operation front-loaded. The trailing English clause largely restates the German sentence, so it is slight redundancy rather than added information, but the overall length is appropriate.

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?

All four required parameters are fully documented in the schema and there is no output schema, so the description need not explain return values in detail — but for a pure computation tool it still leaves unclear what the agent receives (presumably the residual open-share figure) and how the parts relate to the total. Adequate but with a visible gap for a tool of this nature.

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 every parameter carries a German description with 0–1440 bounds, so the schema already does the semantic work. The description's three categories map onto the parameters but add no extra meaning such as units beyond minutes, constraints between values, or how the open remainder is computed.

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 concrete operation (splitting documented attended work minutes into Vorlauf, Platzwechsel and open remainder), which is a real verb+resource statement. However it is dense German jargon mixed with a loosely translated English echo, and nothing distinguishes it from close siblings such as punktwaerme_platzwechsel_wieder_erreichen_anteil or punktwaerme_vorlaufgrenze_beobachtung_vor_erstkontakt, which clearly involve the same categories.

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 statement of when this decomposition should be used versus the many sibling tools that also deal with Vorlauf, Platzwechsel or missing comfort. No prerequisites, no exclusions, no alternative named — the agent must infer selection from the name alone.

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