MCP User Management 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get-users | Get all users |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (create-user), and with only one tool, consistency is inherently perfect as there are no other names to deviate from this pattern.
A server named 'User Management Server' with only one tool (create-user) is severely under-scoped, as user management typically requires at least get, update, delete, and list operations. This single tool feels incomplete and inadequate for the domain.
The tool surface is extremely incomplete for user management, lacking essential operations like retrieving, updating, deleting, or listing users. Agents will be unable to perform basic user management tasks beyond creation, leading to frequent failures.