kimai-timelog-mcp

log_time

Write a finished time entry to Kimai with project, activity, and either start+end, start+duration, or duration alone.

Instructions

Write a finished time entry to Kimai.

Give either start+end, or start+duration, or duration alone (which books the period ending now). Do not guess missing times — ask the user instead.

Args: project: project name or id. activity: activity name or id, must be valid for the project. description: what was worked on. Strongly recommended. date: 'today', 'yesterday', 'monday', '2026-08-24'. start: '09:00', '9am', '14.30'. end: same formats as start. duration: '1h30m', '90m', '1.5h', '1:30'. tags: optional list of Kimai tag names. billable: optional override of the project default.

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": {
      "project": "<project>",
      "activity": "<activity>"
    },
    "name": "log_time"
  }
}

Input Schema

Name	Required	Default
`end`	No
`date`	No	today
`tags`	No
`start`	No
`project`	Yes
`activity`	Yes
`billable`	No
`duration`	No
`description`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavior: duration alone books the period ending now, and missing times must be requested from the user rather than approximated. It does not discuss idempotency or failure effects, but the write effect is plainly labeled and the output schema is present.

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

Conciseness5/5

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

Three introductory sentences plus a compact Args block; every line adds information about valid values or behavior, and the headline 'write a finished time entry' is front-loaded.

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

Completeness5/5

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

For a 9-parameter mutation tool with no annotations, the definition explains all parameter formats, the accepted time-entry shapes, and the no-guessing rule. The presence of an output schema relieves it of needing to document return values, so nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has no parameter descriptions (0% coverage), and the description compensates fully: each Arg line gives meaning plus concrete formats (e.g. start '09:00', '9am', '14.30'; duration '1h30m', '90m', '1.5h', '1:30'), and clarifies that activity must be valid for the project.

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

Purpose5/5

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

Verb 'Write' plus object 'a finished time entry to Kimai' names the mutation and the external system. The phrase 'finished time entry' distinguishes it from start_timer/active_timers/stop_timer among siblings.

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?

States the three valid time-input combinations and instructs to ask the user rather than guess missing times, defining when it is safe to call. It does not explicitly name alternatives such as start_timer, so it stops short of full exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server