MCP server for interacting with DataStax Astra DB databases, providing tools for collection and record management
Server has 16 tools with complete input schemas and descriptions, but quality is inconsistent. Naming follows verb_noun convention (GetCollections, CreateRecord, etc.), which is good. However, descriptions are generic and lack actionable context for LLM selection. Parameter descriptions exist but are minimal (avg ~40 chars). Critical gaps: no output schemas documented, no error handling guidance, no pagination support for list operations, and 'record' parameters lack structure definition. The 'OpenBrowser' tool is out of scope for a database server. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Bulk operations lack per-item error reporting.
Create multiple records in a collection at once
Delete multiple records from a collection at once
Update multiple records in a collection at once
Create a new collection in the database
Create a new record in a collection
Delete a collection from the database
Delete a record from a collection
Unstructured 'record' parameter in CreateRecord, UpdateRecord, BulkCreateRecords, BulkUpdateRecords. Schema defines type:object with no properties or required fields, forcing LLMs to guess valid structure. Should document expected fields, types, and constraints.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., collection_id, record_id). Responses are opaque to the agent.
ListRecords and FindRecord lack pagination guidance. No mention of result limits, next_cursor, or total_count. Large result sets will blow context windows.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Estimate the number of documents in a collection using a fast, approximate count method
Find records in a collection by field value
Get all collections in the Astra DB database
Get a specific record from a collection by ID
Help the user add the Astra DB client to their MCP client
List records from a collection in the database
Open a web browser to a specific URL
Update an existing collection in the database
Update an existing record in a collection
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Clients cannot distinguish safe from dangerous operations.
OpenBrowser and HelpAddToClient are out of scope for a database server. They dilute the tool set and confuse LLM intent. Remove or move to a separate UI/help server.