MCP JSON Document Collection 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_json_doc_databaseD | Create a JSON document database |
| delete_json_doc_databaseC | Delete a JSON document database |
| connect_json_doc_database_to_cloudB | Connect a JSON document database to cloud sync service. Show the dashboard URL after connecting. |
| list_json_doc_databasesA | Returns the list of JSON document databases. Use this to understand which databases are available before trying to access JSON documents. |
| save_json_doc_to_dbC | Save a JSON document to a document database |
| query_json_docs_from_dbC | Query JSON documents sorted by a field from a document database. If no sortField is provided, use the _id field. |
| load_json_doc_from_dbC | Load a JSON document by ID from a document database |
| delete_json_doc_from_dbC | Delete a JSON document by ID from a document database |
| connect_json_doc_database_to_cloudB | Connect a JSON document database to cloud sync service |
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 8 tools
Each tool has a clearly distinct purpose with no ambiguity. Database-level operations (create, delete, list) are separate from document-level operations (load, save, delete, query), and the cloud sync tool stands alone. The descriptions reinforce these boundaries, making misselection unlikely.
All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform across all eight tools, using snake_case consistently. This predictability helps agents understand and select tools efficiently.
With 8 tools, the count is well-scoped for managing JSON document databases and documents. It covers core operations without being overwhelming, and each tool serves a distinct, necessary function in the domain. This aligns with typical server tool counts of 3-15.
The tool set provides strong coverage for CRUD operations on both databases and documents, including querying. A minor gap exists in lacking an update operation for documents (e.g., update_json_doc_in_db), but agents can work around this by using save_json_doc_to_db as a replacement. Overall, it supports core workflows effectively.