Collection of multiple MCP (Model Context Protocol) servers for various data systems and services including Databricks, Redis, MySQL, Snowflake, PostgreSQL, and OData
Scoring was not performed
Redis tools have extremely minimal descriptions (10-30 chars). 'Get the number of keys stored in the Redis database' and 'Get a list of connected clients to the Redis server' lack context for when/why LLM should call them, what they return, or dependencies.
No output schemas documented for any tool. LLMs cannot plan downstream operations or extract structured data. For example, cortex_search returns 'relevant results' but the shape (array of objects? fields returned?) is undocumented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 16 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | 1.9.4+ | v1 |
Object management tools (create_object, drop_object, create_or_alter_object, describe_object) accept 'target_object' as a bare object with no schema specification. What properties must it contain? For 'database', is it just {name: string}? For 'table', must it include column definitions? This is ambiguous.
Destructive operations (drop_object) lack confirmation or dry-run patterns. An agent could accidentally drop a database. No description states this is irreversible or suggests safeguards.
Parameters like 'statement' in run_snowflake_query lack format guidance. No mention of SQL injection risks, acceptable statement types (SELECT vs DDL), or constraints on query complexity.
Redis 'info' tool accepts 'section' parameter with enum values (memory, cpu, etc.) mentioned only in description, not as a formal enum constraint. LLM may hallucinate section names.
cortex_search has 'columns' param described as 'array' but no item schema, and 'filter_query' is 'object' with no structure definition. LLM cannot construct valid payloads without trial-and-error.
No error handling guidance in tool descriptions. If run_snowflake_query fails, does the LLM retry? If drop_object fails due to permissions, what should it do? Recovery patterns are missing.
Credentials/secrets handling is not visible in tool schemas. If Snowflake or Redis requires auth tokens, they should be injected server-side, not as parameters. Unclear how auth is handled.