Hologres MCP Server with STDIO and SSE transport modes support
Two tools with minimal schema documentation and generic descriptions. execute_sql and get_query_plan both have single-string parameters with no type constraints, enums, or validation guidance. Descriptions lack context on when to use each tool, prerequisites, or what the output structure contains. No error handling guidance, no pagination support despite SQL queries potentially returning large result sets. No security warnings about SQL injection despite accepting arbitrary query strings. Tool names are acceptable (verb_noun pattern) but descriptions fall well below the 50-200 char LLM-optimized baseline.
Execute a SQL query against the Hologres database
Get the query execution plan for a SQL query
No input schema validation or constraints. Both tools accept a bare 'query' string with no type, format, length limits, or enum values. LLMs can pass arbitrary SQL, including malicious injection payloads.
Descriptions are generic and under 50 characters. 'Execute a SQL query against the Hologres database' does not explain when to use execute_sql vs get_query_plan, what output format to expect, or prerequisites (e.g., connection state, permissions).
No output schema documented. LLMs cannot plan downstream operations or extract structured data from results. Unclear if results are JSON objects, arrays, or raw text.
No pagination or result limits. SQL queries can return thousands of rows, exhausting context windows. No mention of max_rows, limit, or offset parameters.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
No error handling guidance. Tool descriptions do not explain what errors are retryable, how to recover from connection failures, or what to do if a query is invalid.