Redmine MCP Server

getMembership

Read-only

Fetch membership details by ID, returning user and role information in JSON or XML. Resolve Redmine membership queries quickly.

Instructions

Show 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>"
    },
    "name": "getMembership"
  }
}

Input Schema

Name	Required	Description	Default
`pathParams`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 10, 2026

TDQS

D1.1/5.0

Behavior1/5

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

Annotations declare readOnlyHint=true, but the description adds no additional behavioral context beyond that. It does not disclose what the function returns, whether it throws errors for invalid IDs, or any special handling. Since annotations already cover read-only, the description should add more depth but fails to do so.

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 short (

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?

Given the nested parameter object, no output schema, and zero description coverage, the description is completely inadequate. An agent cannot determine what the response looks like, what to pass for format, or what membershipId refers to. There is no context to guide usage.

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 does not explain any of the parameters. The schema shows pathParams with required format (enum json/xml) and membershipId, but the description gives no hint about what these mean or why format matters. The tool description adds zero value to parameter understanding.

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

Purpose1/5

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

The description 'Show membership' is essentially a tautology of the tool name 'getMembership'. It does not specify what membership means, what resource it operates on, or how it differs from the sibling 'getMemberships'. The verb 'show' is vague and provides no additional clarity over the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. It does not mention when to use getMembership rather than getMemberships (plural) or any other related tool. No context about prerequisites, filters, or the difference between singular and plural retrieval is provided.

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

Deploy Server