Skip to main content
Glama
Avicennasis

redmine-mcp-workflows

by Avicennasis

redmine_create_issue

Create a Redmine issue with cache-aware ID resolution for project, tracker, and other fields.

Instructions

Create an issue with cache-aware id resolution.

Args: project: numeric id or identifier slug (e.g. "claudecode"). tracker: numeric id or name (e.g. "Bug"). subject: required, must be non-empty. description: optional issue body. priority: optional id or name (e.g. "High"); defaults to tracker default when empty. status: optional id or name. Most fleets force initial status via workflow; this is rarely needed. assigned_to_id: optional Redmine user id; 0 means unassigned. difficulty: optional engagement-mode level for the global Difficulty custom field. Values: "Unclassified" / "Easy" / "Normal" / "Hard". When omitted, the field default-fills with "Unclassified" so auto-callers don't trip the required-field validation. Silently no-ops on fleets that don't have a Difficulty field configured. held: optional boolean. True marks the issue as held (blocks closing). False (default) leaves the Held field unset. held_until: optional ISO-8601 date ("2026-10-01"). Sets the Held Until custom field. Empty leaves it unset. Only meaningful when held is True. due_date: optional ISO-8601 date ("2026-05-17"). Empty leaves it unset. start_date: optional ISO-8601 date. Empty leaves it unset (Redmine defaults to the creation date). done_ratio: optional 0-100 progress percent. -1 (sentinel) means unset; 0 is explicit "no progress yet." custom_fields: optional list of {"id": <int>, "value": <str>} entries for arbitrary custom fields. Accepts either a Python list (preferred — Claude can pass it natively) or a JSON- encoded string. Empty string means no custom-field changes beyond what difficulty sets.

Returns the created issue or a structured validation error. Honors REDMINE_MCP_READ_ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heldNo
statusNo
projectYes
subjectYes
trackerYes
due_dateNo
priorityNo
difficultyNo
done_ratioNo
held_untilNo
start_dateNo
descriptionNo
custom_fieldsNo
assigned_to_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: cache-aware id resolution, read-only flag honoring ('REDMINE_MCP_READ_ONLY'), side effects like difficulty no-oping on fleets without the field, and returns structured validation errors.

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 front-loaded with purpose and then organized as an Args list. It is appropriately sized for 14 parameters, though some parameter explanations are verbose. Nearly every sentence adds value, with minimal redundancy.

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

Completeness5/5

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

Given the tool's complexity (14 parameters, 3 required) and existing output schema, the description covers all parameters, return type, and the important read-only behavior. It also addresses edge cases (difficulty no-op, held_until condition) making it self-contained.

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

Parameters5/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 provides extensive semantic detail for every parameter: formats (ISO-8601 for dates), sentinel values (-1 for done_ratio, 0 for assigned_to_id), conditional use (held_until only when held=True), and the custom_fields accepting list or string.

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 begins with 'Create an issue' which is a clear verb+resource pair. It adds specificity with 'cache-aware id resolution,' distinguishing it from siblings like redmine_update_issue and redmine_close_issue.

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?

The description does not explicitly state when to use this tool versus alternatives. It implies usage through its name and the 'create' verb, but lacks direct guidance on scenarios or exclusions compared to similar tools.

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/Avicennasis/redmine-mcp-workflows'

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