kimai-timelog-mcp

delete_timesheet

Delete a time entry permanently by first displaying the entry for confirmation, then removing it from Kimai.

Instructions

Permanently delete a time entry.

Args: timesheet_id: the entry to delete. confirm: must be true. Show the user what will be deleted first.

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": {
      "timesheet_id": "<timesheet_id>"
    },
    "name": "delete_timesheet"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`timesheet_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 28, 2026

TDQS

A4.2/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 of safety disclosure and does it well: 'Permanently delete' signals irreversibility, and 'confirm must be true. Show the user what will be deleted first' adds an important user-consent safety step. It could add more details about permissions or cascading effects, but the core destructive behavior is clearly disclosed.

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 compact and well-structured: a one-sentence action statement followed by two argument bullets. Every sentence adds necessary meaning, the destructive intent is front-loaded, and there is no filler.

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 simple two-parameter deletion tool with an existing output schema, the description covers purpose, destructive impact, required confirmation workflow, and both parameters. The confirm/schema mismatch and the lack of alternative-tool routing leave a minor completeness gap, but the description is otherwise sufficient.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate; it explains timesheet_id as the entry to delete and confirm as a mandatory-to-be-true consent flag. However, the description's 'must be true' conflicts with the schema's non-required status and default false, creating ambiguity about whether confirm must always be explicitly set.

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 opens with a specific destructive verb and resource: 'Permanently delete a time entry.' This clearly identifies what the tool does and inherently distinguishes it from siblings like update_timesheet or list_timesheets, since deletion is a distinct operation.

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

Usage Guidelines3/5

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

There is no explicit 'when to use' guidance or reference to alternatives; the intended context is only implied by the verb 'delete.' The confirm instruction is procedural invocation guidance, not a usage-rule comparing this tool to update_timesheet or list_timesheets, so it lands at the 'implied usage' level.

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

Deploy Server