Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

add_user_to_group

Assign a user to a group by specifying their numeric user ID and the group's ID. Essential for managing user permissions in Redmine.

Instructions

Adds a user to a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesNumeric group ID
user_idYesNumeric user ID to add
Behavior2/5

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

Description only indicates a mutation ('adds'). No disclosure of side effects, permissions, or behavior if the user is already in the group. No annotations to supplement.

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

Conciseness3/5

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

Extremely concise (one sentence), but at the expense of missing important usage details. Acceptable for a simple tool but not exemplary.

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

Completeness2/5

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

Missing output schema and annotations. Does not describe success/failure behavior, idempotency, or error conditions. Incomplete for a mutation tool.

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

Parameters3/5

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

Schema coverage is 100% with clear descriptions for both parameters. The description adds no additional semantic value beyond restating the schema.

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

Purpose5/5

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

Description clearly states the verb ('adds') and resource ('user to a group'), distinguishing it from siblings like 'create_group' and 'remove_user_from_group'.

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 on when to use this tool versus alternatives (e.g., 'add_watcher' or 'create_group_membership'). Missing prerequisites like whether the user or group must exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GonzaloRando03/redmine-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server