redmine-mcp

update_project

Modify an existing Redmine project's name, description, visibility, parent, trackers, or enabled modules. Note that tracker and module lists replace existing values entirely.

Instructions

プロジェクトを更新する(enabled_module_names / tracker_ids は丸ごと置き換えになる点に注意)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "update_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`is_public`	No
`parent_id`	No
`project_id`	Yes
`description`	No
`tracker_ids`	No
`enabled_module_names`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely important behavior — that enabled_module_names and tracker_ids are replaced wholesale rather than merged — which is real value beyond the schema. However, it omits permission requirements, reversibility, and whether unlisted fields are left unchanged.

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?

A single compact sentence with the critical replacement caveat front-loaded in parentheses. Efficient and quick to scan, though extremely terse.

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?

An output schema exists so return values need not be explained, but for a 7-parameter mutation tool with no annotations this description is thin: five parameters are undocumented and no permission or side-effect context is given. The replacement note helps but leaves the definition substantially incomplete.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for 7 parameters. The description adds meaningful semantics (full-replacement) for only 2 of them (enabled_module_names, tracker_ids) and says nothing about name, is_public, parent_id, project_id, or description. With low coverage it must compensate broadly but only does so for a fraction.

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?

States a specific verb+resource ('プロジェクトを更新する' / update a project), which is unambiguous against siblings like create_project, delete_project, and get_project. It stops short of explicit sibling differentiation, so it lands at 4 rather than 5.

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 guidance, no prerequisites, and no routing to alternatives. The parenthetical is a behavioral caveat, not usage guidance, so the agent gets no explicit signal about when this is the right tool.

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