MCP YAML API
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 |
|---|---|
| getUsersB | Retrieve a list of users. |
| getUsersWithQueryParametersA | Retrieve a list of users with pagination. |
| getUserWithPathParametersB | Retrieve a user by ID. |
| createUserB | Create a new user. |
| updateUserC | Update an existing user. |
| replaceUserB | Replace an existing user. |
| deleteUserA | Delete a user by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools have overlapping purposes that could cause confusion, particularly between getUsers, getUsersWithQueryParameters, and getUserWithPathParameters, which all retrieve user data but with different parameters. However, the descriptions clarify the distinctions, such as pagination vs. ID-based retrieval, helping to mitigate misselection.
The naming is mostly consistent with a verb_noun pattern (e.g., createUser, deleteUser), but there are minor deviations in the longer names like getUsersWithQueryParameters and getUserWithPathParameters, which include additional descriptors. Overall, the pattern is readable and predictable.
With 7 tools, the count is well-scoped for a user management API, covering essential CRUD operations and additional query functionalities. Each tool serves a distinct purpose, making the set appropriately sized for the domain.
The tool set provides complete CRUD coverage for user management, including create, read (with variations for listing and specific retrieval), update, replace, and delete. There are no obvious gaps, and the surface supports full lifecycle operations without dead ends.