Redmine MCP Server

createMembership

Create a Redmine project membership by specifying a user ID and role IDs to grant access.

Instructions

Create 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": "createMembership"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 10, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The annotation readOnlyHint=false already indicates a mutation, and the description's 'Create' is consistent. However, the description adds no extra behavioral context such as side effects, required permissions, idempotency, or what happens if the membership already exists. With annotations present, credit is given for additional context, but none is provided.

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?

The description is extremely terse—a single phrase. While concise, it is under-specified for the tool's complexity (nested required objects, two path parameters). The lack of detail makes it more of an under-specification than effective conciseness.

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?

With no output schema and a 0% schema description coverage, the description must carry the full load. It does not explain what a membership is, how it relates to projects, users, and roles, or what a successful creation returns. The agent is left guessing beyond the field names, making this inadequate for correct invocation.

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%, yet the description offers no explanation of parameters like projectId, user_id, role_ids, or format. While field names are somewhat self-explanatory, the description does not clarify their purpose, relationships, or any constraints beyond the schema's enums and types. It fails to compensate for the absent schema descriptions.

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 description 'Create membership' clearly states the verb (create) and resource (membership), which distinguishes it from sibling tools like getMemberships, updateMembership, and deleteMembership. It is unambiguous though terse; it does not elaborate on what a membership is but that is already implied by the context.

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?

No guidance is provided on when to use this tool versus alternatives such as updateMembership or getMemberships. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent to infer that this is for creating a new membership without knowing when a membership already exists.

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

Deploy Server