Skip to main content
Glama
xukaaaa

redmine-mcp-server

by xukaaaa

log_time

Record time spent on a Redmine task by specifying issue ID, hours, and comment, with optional activity and date.

Instructions

Log thời gian làm việc vào task với đầy đủ parameters. Args: issue_id: ID của task hours: Số giờ (ví dụ 1.5) comment: Mô tả công việc đã làm activity_id: ID của activity (ví dụ: 14 cho Development). Default: từ cache spent_on: Ngày làm việc (YYYY-MM-DD). Default: today custom_fields: Custom fields dạng JSON string (ví dụ: '[{"id": 64, "value": "Coding"}]')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYes
hoursYes
commentYes
activity_idNo
spent_onNo
custom_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description does not disclose behavioral traits beyond the existence of defaults. With no annotations, it fails to mention idempotency, side effects (e.g., creation vs. update), or error conditions.

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 concise (4 sentences) and front-loaded with the main purpose. It clearly lists parameters with examples, avoiding unnecessary fluff.

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?

Given the presence of an output schema (not shown) and the tool's straightforward nature (logging time with defaults), the description covers essential parameter details and examples, making it sufficiently 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 description coverage is 0%, but the description compensates by explaining defaults (activity_id from cache, spent_on today) and providing examples (custom_fields JSON, activity_id 14). However, issue_id, hours, and comment lack added semantics beyond names.

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

Purpose4/5

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

The description clearly states the tool logs working time into a task ('Log thời gian làm việc vào task'), specifying the action and resource. It distinguishes from sibling log retrieval tools by indicating it creates logs.

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 like update_issue_status or add_note. Missing context on prerequisites, such as requiring an existing issue or permissions.

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/xukaaaa/redmine-mcp-server'

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