Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

list_users

Retrieve a filtered list of Redmine users by status, name, group, or login. Requires admin access to manage user accounts.

Instructions

Lists users in Redmine with optional filters. Requires admin privileges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of items to skip (default 0)
limitNoNumber of items per page (default 25, max 100)
includeNoComma-separated: auth_source
statusNoFilter by status. Values: 1=active, 2=registered, 3=locked. Operators: = (default), ! (not equal). Examples: 1, 1|2, !3
nameNoFilter by name, login, or email (contains search). Examples: john, admin
group_idNoFilter by group membership. Value is the group ID
loginNoFilter by login. Operators: ~ (contains), = (exact), ! (not equal), ^ (starts with), $ (ends with)
firstnameNoFilter by first name. Operators: ~ (contains), = (exact), ! (not equal), ^ (starts with), $ (ends with)
lastnameNoFilter by last name. Operators: ~ (contains), = (exact), ! (not equal), ^ (starts with), $ (ends with)
mailNoFilter by email address. Operators: ~ (contains), = (exact), ! (not equal), ^ (starts with), $ (ends with)
adminNoFilter by admin privilege: 1=admin, 0=non-admin
auth_source_idNoFilter by authentication source. Operators: = (default), ! (not equal), * (any), !* (none)
twofa_schemeNoFilter by two-factor authentication scheme. Operators: = (default), ! (not equal), * (any), !* (none)
created_onNoFilter by creation date. Examples: >=2024-01-01, >t-30, lm
last_login_onNoFilter by last login date. Examples: >=2024-01-01, >t-30, !* (never logged in)
Behavior3/5

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

With no annotations, description provides the admin privilege requirement but no other behavioral traits (e.g., pagination limits, response format, rate limiting). Schema covers parameters, so the gap is in behavioral context beyond params.

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

Conciseness4/5

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

Two sentences, no wasted words, front-loaded with purpose. Could be improved by including more behavioral info in the same space, but it is concise.

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?

Given 15 parameters, no output schema, and many sibling tools, the description is too sparse. It lacks context on return format, pagination, error handling, or typical usage patterns. Inadequate for the tool's complexity.

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%, so baseline is 3. Description adds no parameter semantics beyond what the schema already provides. No added value for parameter understanding.

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 clearly states it lists users with optional filters and requires admin privileges. The verb and resource are specific. However, it does not explicitly differentiate from siblings like search or list_groups, slightly reducing clarity.

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?

Only mentions admin requirement. No guidance on when to use vs alternatives, no exclusions, and no context on prerequisites beyond admin. 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.

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