redmine-mcp-workflows

redmine_create_project

Create a new Redmine project with a required name and URL slug, plus optional settings like parent project, modules, and visibility.

Instructions

Create a new project.

Args: name: required project display name. identifier: required URL slug (lowercase, hyphens, no spaces). description: optional project description. homepage: optional homepage URL. is_public: whether the project is publicly visible. None (omitted) uses the Redmine default (public). parent_id: optional parent project id (0 for top-level). inherit_members: if True, inherit members from parent. None (omitted) uses the Redmine default (no inheritance). tracker_ids: optional list of tracker ids to enable. enabled_module_names: optional list of modules (e.g. ["issue_tracking", "wiki", "boards"]).

Honors REDMINE_MCP_READ_ONLY.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`homepage`	No
`is_public`	No
`parent_id`	No
`identifier`	Yes
`description`	No
`tracker_ids`	No
`inherit_members`	No
`enabled_module_names`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.1.0Sep 30, 2026
- addedInput schema / properties / inherit_members / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / inherit_members / default
```
Previous value: -falseNew value: +null
```
- removedInput schema / properties / inherit_members / type
```
Removed value: -"boolean"
```
- addedInput schema / properties / is_public / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / is_public / default
```
Previous value: -trueNew value: +null
```
- removedInput schema / properties / is_public / type
```
Removed value: -"boolean"
```
First observedv1.0.0Jul 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations are absent, so the description carries the full behavioral burden. It usefully discloses that the tool honors REDMINE_MCP_READ_ONLY and clarifies the default-resolution semantics of None for is_public and inherit_members, which is real added context. However, it says nothing about required permissions, what happens on identifier collision, validation failure behavior, or side effects such as default modules/trackers being enabled.

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?

Front-loaded with the purpose in one line, then a compact per-parameter list with no filler sentences. The list is long but justified given nine undocumented parameters; only minor tightening is possible.

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?

An output schema exists, so return values need not be described, and all nine inputs are annotated. What remains missing is operational context appropriate to a mutation tool: permission requirements and error/failure behavior. Given the output schema and full parameter coverage, the definition is nearly complete.

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% and there are 9 parameters, so the description must compensate and it does: it marks which two are required, gives the identifier format (lowercase, hyphens, no spaces), explains the None-means-Redmine-default convention for two nullable params, notes parent_id 0 means top-level, and supplies an example value for enabled_module_names. This is meaningfully more than the schema alone conveys.

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 opening line states a specific verb and resource ("Create a new project"), which unambiguously distinguishes it from siblings like redmine_update_project, redmine_delete_project, and redmine_archive_project. It does not explicitly name an alternative, but the create/update/delete/archive split among siblings is self-evident from the names.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g. permission level needed to create projects), and no mention of the sibling tools an agent might confuse this with. The only routing-relevant signal is the REDMINE_MCP_READ_ONLY note, which constrains execution but does not help select this tool over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server