MCP server for querying and managing ClickHouse databases on freebase.cloud via Gemini CLI
This server exposes 6 tools, but only 2 are actual domain tools (sky_query, sky_store). The other 4 (tools/list, tools/call, initialize, notifications/initialized) are MCP protocol mechanics, not user-facing capabilities. Of the 2 real tools, both have minimal descriptions (under 100 chars) and lack output schema documentation. Input schemas are present but sparse. No error handling guidance, no parameter validation rules, no security considerations. The probe script shows HTTP transport and basic JSON-RPC, but tool definitions appear inferred from shell examples rather than formally registered in code.
Initialize MCP protocol handshake with server
Notify server that client initialization is complete
Execute a SQL query against the ClickHouse database
Execute a SQL statement to store/modify data in the ClickHouse database
Call a tool by name with provided arguments
List all available tools exposed by the MCP server
No output schema documentation. sky_query and sky_store return results but LLMs cannot predict structure (rows, columns, error format, pagination). Forces guessing and parsing errors.
Descriptions too brief (<100 chars). 'Execute a SQL query' does not explain when to use sky_query vs sky_store, what happens on error, or what data is returned. LLMs cannot reliably select the right tool.
No parameter validation rules. 'query' parameter accepts any string, no guidance on SQL dialect, size limits, timeout, or what constitutes a valid statement. LLMs will pass malformed SQL.
No error handling guidance. If a query fails (syntax error, timeout, permission denied), LLMs receive no recovery path. Error responses must tell the agent what to do next.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
Tool definitions inferred from shell script examples, not from explicit server code. Cannot verify actual registration, schema enforcement, or runtime behavior. Caps confidence in tool availability.