Skip to main content
Glama

Create Kimai Timesheet

kimai_create_timesheet

Add a timesheet entry to Kimai after explicit human approval. Configurable timestamps, project, activity, tags, and rates; automatic backup of request and record.

Instructions

Create a Kimai timesheet record. Sensitive edit: call only after explicit human authorization. The request and created record are saved to a temp backup file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoOptional timesheet end timestamp in Kimai HTML5 datetime-local format, e.g. 2026-06-01T10:30:00.
fullNoRequest fully serialized Kimai response where supported.
tagsNoOptional tags; sent to Kimai as a comma-separated list.
userNoOptional user ID; requires permission to edit other users' time.
beginYesTimesheet begin timestamp in Kimai HTML5 datetime-local format, e.g. 2026-06-01T09:00:00.
projectYesKimai project ID.
activityYesKimai activity ID.
billableNoOptional billable flag.
exportedNoOptional exported flag. This can lock/unlock timesheet records.
fixed_rateNoOptional fixed rate override.
descriptionNoOptional timesheet description.
hourly_rateNoOptional hourly rate override.
response_formatNoOutput format: markdown for human-readable summaries, json for structured output.markdown
authorization_noteYesShort note capturing the user's explicit authorization and reason for the edit.
authorization_confirmedYesMust be true only after the human user explicitly authorizes this sensitive Kimai edit.
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are supplemented by description stating sensitivity and backup behavior. Adds value beyond annotations by clarifying authorization requirement and persistent backup, though does not cover all edge cases.

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?

Two concise, front-loaded sentences with no redundant information. Every sentence serves a purpose.

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?

Given 15 parameters, no output schema, and no description of return values, the description is slightly incomplete. It mentions backup but not the tool's response format, which is partially addressed by the 'response_format' parameter but not in the description itself.

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 baseline is 3. The description does not add parameter-level detail beyond the schema, so no extra value.

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?

Description states 'Create a Kimai timesheet record' with a specific verb and resource. It also notes 'Sensitive edit', distinguishing it from read-only or other mutation tools like update, stop, restart.

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?

Explicitly warns 'call only after explicit human authorization', providing clear usage context. Does not list when not to use or alternatives, but the context is sufficiently clear given sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NightSquawk/kimai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server