redmine-mcp

add_project_file

Register an uploaded attachment in a Redmine project's Files section using a token from upload_attachment. Requires the Files module enabled.

Instructions

プロジェクトの「ファイル」にアップロード済みファイルを登録する。

先に upload_attachment でトークンを得る。プロジェクトで files モジュールが有効である必要あり。文書(Documents)モジュールは API 非対応のためこちらを使う。

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>",
      "token": "<token>"
    },
    "name": "add_project_file"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`filename`	No
`project_id`	Yes
`description`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.5/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 behavioral burden. It discloses the token prerequisite and module requirement, which are useful. However, it does not state whether the operation is reversible, what permissions are needed beyond the module, or what side effects occur — shortcomings for a mutation tool without annotation coverage.

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?

Three short sentences, each earning its place, with the prerequisite front-loaded. No redundant or filler content.

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

Completeness3/5

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

The description covers purpose and key usage conditions, and an output schema exists so return values need not be explained. But it leaves all four parameters without semantic guidance and omits side-effect details, creating clear gaps for a write operation with no annotations and 0% schema coverage.

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 description coverage is 0%, so the description must compensate. It only indirectly references the token parameter by saying it comes from upload_attachment, and says nothing about project_id, filename, or description. The four parameters remain essentially undocumented.

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 and resource: registering an already-uploaded file to a project's Files module. It distinguishes itself from upload_attachment by specifying the token prerequisite, and notes the Documents module is not API-supported. However, it does not explicitly contrast with other file-related siblings like list_files or download_attachment.

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?

Provides clear prerequisites: first obtain a token via upload_attachment, and the files module must be enabled. It also indicates an alternative context by saying the Documents module is not API-supported, so use this instead. No explicit when-not-to-use case is given, but the conditions are sufficiently clear.

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