Redmine MCP Server

updateMembership

Update membership roles in Redmine by specifying the membership ID and new role IDs. This tool modifies role assignments for an existing membership via the Redmine REST API.

Instructions

Update membership

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": {
      "pathParams": "<pathParams>",
      "bodyParams": "<bodyParams>"
    },
    "name": "updateMembership"
  }
}

Input Schema

Name	Required	Description	Default
`bodyParams`	Yes
`pathParams`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.4Aug 2, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Update' without explaining side effects, whether it replaces the entire role list, what happens to omitted fields, or whether authorization is required. This is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While very short, this is under-specification rather than conciseness. The single phrase adds no informative value and does not fulfill the requirement that every sentence earn its place by conveying useful, non-redundant information.

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

Completeness1/5

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

The tool has a nested schema with required path and body parameters, but the description is completely inadequate for an agent to invoke it correctly. It does not explain the return value, potential errors, or how the request should be structured, leaving the agent to guess from raw schema names.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no parameter information. The schema shows two objects (pathParams and bodyParams) with nested properties like membershipId, format, and role_ids, but the description does not explain their meaning or how to construct valid requests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update membership' is a tautology that merely restates the tool name with a space. It does not specify what aspects of membership are updated, which resource is modified, or how it differs from sibling tools like createMembership or getMembership.

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 guidance on when to use this tool versus alternatives. The description gives no context about typical scenarios, prerequisites, or relationships to other membership-related tools such as createMembership or deleteMembership.

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

Deploy Server