UniCloudDB-MCP
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 |
|---|---|
| queryD | – |
| addD | – |
| updateD | – |
| removeD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| help |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools have clearly distinct purposes based on their names: add, query, remove, and update correspond to the fundamental CRUD operations. There is no overlap or ambiguity between them, as each targets a specific action in a database context.
All tool names follow a consistent pattern using simple, single-word verbs (add, query, remove, update). There are no deviations in style or convention, making them predictable and easy to understand as a set.
With 4 tools, this server is well-scoped for a database management purpose, covering the essential CRUD operations. Each tool earns its place without being excessive or insufficient for the apparent domain of data handling.
The tool set provides complete CRUD coverage for a database domain: add (create), query (read), update (update), and remove (delete). There are no obvious gaps, as these operations form a full lifecycle for data management without dead ends.