Skip to main content
Glama
flor3z-github

Redmine MCP Server

redmine_create_issue

Create a new Redmine issue with required project ID and subject, plus optional fields for description, attachments, due date, priority, and more.

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?

No annotations provided, and the description does not disclose behavioral traits such as mutability, required permissions, rate limits, or return behavior. It merely states the creation action without any additional context.

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 a single, concise sentence. It contains no extraneous information and efficiently conveys the tool's purpose.

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 tool's complexity (18 parameters, no output schema, no annotations), the description is insufficient. It lacks details about return values, error conditions, and prerequisites (e.g., project must exist).

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?

The description adds no parameter information beyond the already comprehensive input schema (100% coverage). While the schema is detailed, the description contributes no extra semantic value, earning the baseline score.

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 action ('Create') and resource ('new issue in Redmine'). It is specific and unambiguous, but does not differentiate from sibling tools like redmine_update_issue or redmine_list_issues.

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 on when to use this tool versus alternatives (e.g., redmine_update_issue). No prerequisites or context for correct usage are mentioned.

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

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