Redmine MCP Server

createUser

Create a Redmine user account by supplying login, name, email, and preferences. Control password, status, and notification settings for the new user.

Instructions

Create user

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>",
      "bodyParams": "<bodyParams>"
    },
    "name": "createUser"
  }
}

Input Schema

Name	Required	Description	Default
`bodyParams`	Yes
`pathParams`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

The description adds no behavioral information beyond the annotation readOnlyHint: false. It doesn't disclose side effects, permission requirements, validation rules, or the shape of the response, so the description carries minimal transparency burden.

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?

The description is extremely concise and front-loaded, with no wasted words. However, it is too sparse to provide meaningful structure or guidance, making it minimally adequate at best.

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 the complexity of the input schema (nested objects, required fields, no output schema), the description is heavily under-specified. It omits essential details about the format parameter, the required user fields, or expected behavior, making it incomplete for an agent to invoke correctly.

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

Parameters2/5

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

The schema has 0% description coverage, and the description does not explain any parameters. Nested fields like 'user', 'pref', and 'send_information' remain opaque, and the description fails to compensate for the lack of parameter documentation.

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 'Create user' clearly states the verb and resource. While it doesn't explicitly differentiate from other create tools (like createProject), the resource 'user' is unambiguous among siblings such as updateUser, deleteUser, and getUsers.

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?

The description provides no guidance on when to use this tool versus alternatives like updateUser or deleteUser. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage.

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

Deploy Server