mcp-database-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 |
|---|---|
| save_json_docC | Save a JSON document |
| load_json_docC | Load a JSON document by ID |
| delete_json_docC | Delete a JSON document by ID |
| query_json_docsC | Query JSON documents sorted by a field |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: load retrieves, save creates/updates, delete removes, and query searches documents. The descriptions make it easy for an agent to select the right tool for each operation without confusion.
All tool names follow a consistent verb_noun pattern (e.g., load_json_doc, save_json_doc) with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance.
With 4 tools, this server is well-scoped for basic JSON document operations. Each tool earns its place by covering essential CRUD-like functions (load, save, delete, query), which is appropriate for a database server focused on JSON documents.
The tool set provides complete coverage for the domain of JSON document management: it includes create/update (save), read (load), delete, and query operations. There are no obvious gaps, and agents can perform full lifecycle tasks without dead ends.