Skip to main content
Glama

getecoback-raumklima

pc_dauerlog_aufgabenzeit_und_wandzeit_trennen

Read-only

Einen Lastzeitpunkt aus der kumulierten Arbeitszeit wieder auf die gemeinsame Uhr setzen, wenn genau eine protokollierte Pause dazwischen lag — Map a task-runtime marker to wall time across one verified pause.

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": {
      "start_uhr_s": "<start_uhr_s>",
      "pause_ab_aktiv_s": "<pause_ab_aktiv_s>",
      "pause_dauer_s": "<pause_dauer_s>",
      "marker_aktiv_s": "<marker_aktiv_s>",
      "uhr_lief_nur_bei_arbeit": "<uhr_lief_nur_bei_arbeit>"
    },
    "name": "pc_dauerlog_aufgabenzeit_und_wandzeit_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_uhr_sYesBeginn der durchgängig protokollierten Sitzung auf der gemeinsamen Uhr.
pause_dauer_sYesSeparat protokollierte Pausendauer auf der gemeinsamen Uhr.
marker_aktiv_sYesKumulierter Arbeitszeitwert des zuzuordnenden Ereignisses.
pause_ab_aktiv_sYesKumulierter Arbeitszeitwert beim Beginn der einzigen Pause.
uhr_lief_nur_bei_arbeitYesDer aktive Zähler stoppte in genau dieser Pause, ohne Neustart oder weitere Pausen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only and closed-world behavior. The description adds the important constraint that exactly one pause is assumed, but it does not state what happens if that assumption fails, whether inputs are validated, or what the result represents beyond wall time.

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 core operation and precondition are front-loaded, and no sentence is wasted in substance. The German/English duplication is largely redundant, which keeps it from a 5 for conciseness.

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

Completeness4/5

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

For a five-required-parameter read-only calculation, the description supplies the central transformation and its key precondition, while annotations cover safety and the schema covers inputs. It still leaves edge-case behavior and the exact returned value implicit, so it is strong but not fully complete.

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 coverage is 100%, so each parameter already has documentation. The description reinforces the relationship between accumulated work time, shared clock, and one pause, but does not add units, error conditions, or per-parameter interpretation 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 names a precise transformation: map an accumulated task-runtime marker back to shared wall-clock time, with the condition of exactly one logged pause. It is specific enough to distinguish from generic time conversion, but it does not explicitly contrast any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear precondition for use: exactly one verified/logged pause must lie between the marker and the session start. It does not explain what to use when there are zero or multiple pauses, nor name an alternative, so it stops short of full routing guidance.

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