Redmine MCP Server

redmine_delete_time_entry

Remove a specific Redmine time entry by ID, helping correct or clean up inaccurate logged hours efficiently.

Instructions

Delete a time entry

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": {
      "id": "<id>"
    },
    "name": "redmine_delete_time_entry"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Time entry ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior on its own. It only says 'Delete a time entry,' which adds no beyond the tool name. It fails to mention irreversibility, permissions, or any side effects of deletion.

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 description is a single concise sentence with no wasted words. It is well-structured and front-loaded, though it could arguably provide more detail without losing conciseness.

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?

This is a simple one-parameter tool with full schema coverage, so the description need not explain return values. However, for a destructive operation with no annotations, the lack of any behavioral details (e.g., permanence, permissions) leaves the description only minimally 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% ('Time entry ID to delete'), so the description does not need to detail parameters. The description itself adds no parameter semantics beyond what the schema already provides, yielding the baseline score of 3.

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 'Delete a time entry' clearly specifies the verb (delete) and the resource (time entry), which distinguishes it from sibling tools like redmine_delete_issue and redmine_delete_wiki_page. The action and target are unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or conditions. The name implies the action, but there is no explicit context or exclusions.

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