Simple 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-userC | Create a new user in the database |
| 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 both create users, but one creates a user with specified data and the other generates a random user, which is a clear distinction. However, the names are nearly identical and could be confused without reading descriptions carefully.
Both tools follow a consistent verb-noun pattern with the 'create-' prefix, making the naming predictable and uniform.
With only two tools, the server feels thin and at the low end of the reasonable range. The count is borderline, as the server's simple scope could justify it, but it might be too minimal for practical use.
The tools only cover user creation, leaving out essential operations like getting, listing, updating, or deleting users. This creates a significant gap in the expected lifecycle for user management.