Skip to main content
Glama
gmlee-ncurity

Redmine MCP Server

redmine_create_issue

Create a new Redmine issue by providing project ID and subject, with optional fields for description, assignee, priority, due date, attachments, and custom settings.

Instructions

Create a new issue in Redmine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesIssue subject/title
uploadsNoFile attachments to add (use redmine_upload_file first to get tokens)
due_dateNoDue date (YYYY-MM-DD)
status_idNoStatus ID
done_ratioNoCompletion percentage (0-100)
is_privateNoWhether the issue is private
project_idYesProject ID
start_dateNoStart date (YYYY-MM-DD)
tracker_idNoTracker ID (e.g., Bug, Feature, Task)
category_idNoCategory ID
descriptionNoIssue description (in Markdown format)
priority_idNoPriority ID
assigned_to_idNoAssigned user ID
estimated_hoursNoEstimated hours
parent_issue_idNoParent issue ID
fixed_version_idNoTarget version ID
watcher_user_idsNoUser IDs to add as watchers
custom_field_valuesNoCustom field values as key-value pairs
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the creation action without mentioning required permissions, side effects, response format, or error behavior, leaving the agent uninformed about the operation's specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is succinct at one sentence, but it is under-specified for a complex tool with 18 parameters. It omits important supplementary guidance that could be presented concisely, such as required fields or special use cases, making it more under-specified than appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, output schema, and the tool's complexity, the minimal description fails to cover essential behavioral context like response format, validation requirements, or the need to use redmine_upload_file for attachments. The schema covers parameters but not the overall tool context.

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?

All 18 parameters have descriptions in the schema (100% coverage), so the schema provides complete parameter semantics. The description itself adds no additional parameter context beyond what the schema already documents, so the baseline of 3 is appropriate.

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

Purpose2/5

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

The description 'Create a new issue in Redmine' essentially restates the tool name 'redmine_create_issue', offering no additional detail about scope or distinct functionality compared to sibling issue tools. It is a tautological expansion of the name rather than a clarifying statement.

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 regarding when to use this tool versus redmine_update_issue or redmine_delete_issue, nor any prerequisites such as having a project_id or uploading files first. The only usage hint appears in the uploads parameter description, not in the main description.

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

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