kimai-mcp-server

Duplicate Kimai Timesheet

kimai_duplicate_timesheet

Duplicates a timesheet record after explicit human authorization, saving both source and copy to a backup file.

Instructions

Duplicate an existing Kimai timesheet. Sensitive edit: call only after explicit human authorization. The source and created record are saved to a temp backup file.

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": {
      "authorization_confirmed": "<authorization_confirmed>",
      "authorization_note": "<authorization_note>",
      "id": "<id>"
    },
    "name": "kimai_duplicate_timesheet"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Kimai entity ID.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown
`authorization_note`	Yes	Short note capturing the user's explicit authorization and reason for the edit.
`authorization_confirmed`	Yes	Must be true only after the human user explicitly authorizes this sensitive Kimai edit.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds that this is a sensitive edit requiring authorization and that backups are saved. This provides meaningful behavioral context beyond the annotations, such as the need for human oversight and data preservation.

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?

The description is two sentences long, with the most critical instruction ('sensitive edit, call only after explicit human authorization') placed first. Every sentence adds value without redundancy.

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?

The tool has 4 parameters and no output schema. The description covers the core operation (duplicate), the authorization requirement, and backup behavior. For a mutation tool with moderate complexity, this provides sufficient completeness, though it could optionally mention what happens to the original timesheet (it remains unchanged, implied by 'duplicate').

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%, meaning the input schema already documents all parameters (id, response_format, authorization_note, authorization_confirmed). The description does not add additional meaning beyond what the schema provides, so it meets the baseline but does not exceed it.

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?

The description uses a specific verb ('Duplicate') and explicitly names the resource ('existing Kimai timesheet'). This clearly distinguishes it from related tools like 'kimai_create_timesheet' (create new) and 'kimai_update_timesheet' (modify).

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?

The description explicitly states 'Sensitive edit: call only after explicit human authorization,' providing a clear precondition. It also notes that the source and created record are saved to a temp backup file, which implies a safety net. However, it does not compare to alternatives or specify when not to use it.

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