Skip to main content
Glama
Avicennasis

redmine-mcp-workflows

by Avicennasis

redmine_update_issue

Update a Redmine issue with proactive workflow validation to reject invalid status changes before they are applied.

Instructions

Update an issue, with reactive workflow validation on status changes.

Args: issue_id: numeric Redmine issue id. subject: optional new subject. description: optional new description. status: optional id or name (e.g. "In Progress"). Triggers workflow pre-flight against the cache. priority: optional id or name. assigned_to_id: optional user id; 0 means unchanged. notes: optional comment to attach with this update (becomes a journal entry). difficulty: optional engagement-mode level for the global Difficulty custom field. Values: "Unclassified" / "Easy" / "Normal" / "Hard". NO default-fill on update — empty means "don't change Difficulty." held: optional boolean. True marks the issue as held (blocks closing). False (default) means unchanged. To clear a held flag, pass held=True is wrong — instead pass custom_fields with {"id": 2, "value": ""} directly, or set held=False won't fire (sentinel is falsy). held_until: optional ISO-8601 date ("2026-10-01"). Sets the Held Until custom field. Empty means unchanged. due_date: optional ISO-8601 date ("2026-05-17"). Empty leaves it unchanged; pass the literal string "" (i.e. just don't send this arg) to leave it untouched. To clear an existing due_date you currently need redmine_request with {"issue": {"due_date": null}} — the MCP can't distinguish "unset" from "leave alone" without explicit null support. start_date: same shape as due_date. done_ratio: optional 0-100 progress percent. -1 (sentinel) means unchanged; 0 is explicit "reset to no progress." fixed_version_id: optional version id (string for id-or-empty). Empty leaves unchanged; explicit "0" clears the version. custom_fields: optional list of {"id": <int>, "value": <str>} entries. Accepts either a Python list (preferred) or a JSON- encoded string. Empty means no custom-field changes.

On a status change the cache pre-flight short-circuits any previously-observed disallowed transition with a :class:WorkflowTransitionDisallowed payload. After a real PUT the outcome is recorded so future calls benefit. Honors REDMINE_MCP_READ_ONLY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heldNo
notesNo
statusNo
subjectNo
due_dateNo
issue_idYes
priorityNo
difficultyNo
done_ratioNo
held_untilNo
start_dateNo
descriptionNo
custom_fieldsNo
assigned_to_idNo
fixed_version_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 discloses behavioral traits: reactive workflow validation, cache pre-flight, read-only mode honoring, sentinel handling for unchanged parameters, and edge cases like clearing held or due_date. This is thorough and transparent.

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 quite lengthy and dense, with a paragraph for each parameter. While the detail is necessary, it could be more structured (e.g., bullet points) to improve readability and scanability. The purpose is front-loaded, which is good.

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 (15 parameters, 1 required, no annotations), the description is highly complete. It covers all parameters, special behaviors, cache interactions, and even directs users to redmine_request for edge cases. An output schema exists, so return values are handled separately.

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?

The schema description coverage is 0%, but the description explains each parameter in detail, including semantics for optional parameters, sentinel values, and special handling (e.g., status triggers pre-flight, difficulty enumeration, held clearing). This fully compensates for the lack of schema descriptions.

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 clearly states 'Update an issue, with reactive workflow validation on status changes,' specifying the verb and resource. It distinguishes from sibling tools like redmine_bulk_update_issues and redmine_close_issue by focusing on single-issue updates with workflow validation.

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

Usage Guidelines4/5

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

The description provides detailed context on when to use the tool, including special behaviors for status changes, cache pre-flight, and sentinel values. It also mentions when not to use it (e.g., clearing due_date requires redmine_request), though it does not explicitly compare to all siblings or provide a comprehensive 'when not to use' list.

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