Redmine MCP Server

getGroup

Fetch a Redmine group's details by group ID, optionally including its users or memberships. Useful for retrieving group information to manage permissions and team structure.

Instructions

Show group

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>",
      "queryParams": "<queryParams>"
    },
    "name": "getGroup"
  }
}

Input Schema

Name	Required	Description	Default
`pathParams`	Yes
`queryParams`	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?

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing. It does not mention that this is a read operation, what parameters are required, or any side effects or response characteristics. This is a substantial gap for a tool with a nested schema.

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, which is structurally concise, but it is under-specified. 'Show group' is a terse restatement of the name and does not use the limited space to convey meaningful information. It fails the test of every sentence earning its place.

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 tool's nested parameters, enums, and the lack of an output schema, the description is profoundly incomplete. It does not explain how to identify a group, what the include query parameter does, or what the response will contain, making the tool effectively unusable based on the description alone.

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 explanation of the parameters (format, groupId, include). It does not compensate for the schema's lack of descriptive text, leaving the agent without guidance on what values to supply or what the parameters mean.

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 'Show group' essentially restates the tool name 'getGroup' without adding specific detail. It does not distinguish this tool from the sibling tool 'getGroups' (which presumably lists groups), nor does it clarify what 'show' encompasses.

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. It does not mention that this retrieves a single group by ID, nor does it advise using getGroups for listing all groups. The description offers no context for tool selection.

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

Deploy Server