Skip to main content
Glama

getecoback-climate-weather

arbeitsplatz_sitzdauer_waermerueckmeldung_abdeckung

Read-only

Bei einem beobachteten Arbeitsplatzwechsel die eigene Rückmeldung von allen Zeitabschnitten ohne dokumentierte Sitznutzung trennen — Count evidenced personal comfort across an interrupted desk session.

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": {
      "arbeitszeit_min": "<arbeitszeit_min>",
      "eigener_platz_min": "<eigener_platz_min>",
      "persoenlich_warm_min": "<persoenlich_warm_min>",
      "erfassung_sitzblock_vollstaendig": "<erfassung_sitzblock_vollstaendig>"
    },
    "name": "arbeitsplatz_sitzdauer_waermerueckmeldung_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeitszeit_minYesDauer der gesamten betrachteten Arbeitszeit in Minuten.
eigener_platz_minYesDavon protokollierte Minuten am eigentlichen Arbeitsplatz.
persoenlich_warm_minYesDavon Minuten mit ausdrücklich erfasster brauchbarer persönlicher Wärme.
erfassung_sitzblock_vollstaendigYesDer dokumentierte Sitzblock war vollständig mit Rückmeldungen abgedeckt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a closed, side-effect-free computation, lowering the bar. The description adds that feedback is separated from periods without documented sitting use, which is useful domain behavior, but it does not explain how the completeness flag changes the calculation or what happens with edge cases like zero minutes at the desk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, so size is not a problem, but the German and English halves are redundant paraphrases rather than a precise translation, and neither is front-loaded with the actual operation. The bilingual duplication adds noise without adding information.

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?

There is no output schema, and the description never says whether the result is a count, a ratio, or a coverage verdict, despite the name implying 'Abdeckung' (coverage). It also omits how 'erfassung_sitzblock_vollstaendig' affects the outcome and what happens when 'eigener_platz_min' is zero. For a four-required-parameter computation tool with no output schema, this leaves too much unspecified.

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%, with each of the four parameters documented in German in the schema itself, so the baseline of 3 applies. The description adds no additional meaning about the relationship among total work minutes, desk minutes, warm minutes, and the completeness boolean beyond the vague notion of separating undocumented periods.

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

Purpose2/5

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

The description restates the name's components (Wärmerückmeldung, Abdeckung) as 'Count evidenced personal comfort across an interrupted desk session' without stating the actual computation. The German clause 'die eigene Rückmeldung von allen Zeitabschnitten ohne dokumentierte Sitznutzung trennen' is opaque and does not tell an agent what operation or result to expect. It does not distinguish this tool from the many sibling '..._abdeckung' tools.

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 explicit statement of when to use this tool, when not to, or which sibling alternative fits a different scenario. The mention of an 'observed desk change / interrupted desk session' hints at a context but never turns it into a selection rule, so the agent must infer usage 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