Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by compasify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getMembership

Retrieve Redmine membership details by ID. Get specific membership information in JSON or XML format.

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

NameRequiredDescriptionDefault
pathParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. 'Show membership' reveals no traits such as read-only nature, required permissions, or return format, leaving behavioral expectations completely unspecified.

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, but this is under-specification rather than effective conciseness. It consists of two words and omits essential information that would make the tool usable.

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 annotations, no output schema, and a nested parameter structure, the description is wholly inadequate. It does not explain what the tool returns, how the membership is identified, or how the output format parameter affects behavior, making the tool nearly impossible to select and invoke correctly without external knowledge.

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 adds no meaning to the parameters. The required membershipId and format (json/xml) are not mentioned, so the agent must rely entirely on the schema without any contextual explanation.

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

Purpose3/5

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

The description 'Show membership' provides a verb and resource but is vague, not specifying that it retrieves a single membership by ID. It does not differentiate from the sibling getMemberships (plural), leaving the purpose to be inferred from the name and schema.

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 getMemberships or other membership-related tools. No context, exclusions, or alternatives are mentioned, so the agent receives no decision support.

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

Deploy Server

Other Tools