User Management MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-userC | Create a new user in the system |
| create-random-userA | Create a random user with fake data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-fake-user | Generate a fake user based on a given name |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| users | Get all users data from the database |
TDQS
Scored across 2 tools
The two tools have highly overlapping purposes: both create users. 'create-random-user' and 'create-user' differ only in the data source (fake vs. system), which is a subtle distinction that agents will likely confuse. This is a classic case of ambiguous tool boundaries.
Both tools follow a consistent verb_noun pattern with hyphen-separated names. 'create-random-user' and 'create-user' are perfectly aligned in naming style, making them predictable and readable.
With only 2 tools, the server feels severely under-scoped for a 'User Management' domain. A user management system typically requires at least CRUD operations (create, read, update, delete) and possibly list/search tools. This minimal set is inadequate for the implied purpose.
The tool surface is extremely incomplete for user management. There are no tools to retrieve, update, delete, or list users, creating significant gaps that will cause agent failures. Agents cannot perform basic user management workflows beyond creation.