DBPilot is a database diagnostics MCP server with 11 read-only tools covering instance discovery, performance metrics, blocking analysis, slow SQL, deadlock investigation, and index analysis. Naming is consistently strong (verb_noun pattern: list_, get_). Descriptions are well-written and contextual, typically 100-250 characters with clear guidance on when to use each tool. However, schemas are inconsistently documented, input parameters are defined in code but output schemas are only partially visible in the provided source. The server correctly emphasizes read-only safety and notes that SQL text is data, not instructions. Tools are properly composed (each does one thing), and error handling includes actionable recovery hints. Main gaps: output schemas not fully documented in source, no input validation rules stated in descriptions, no enum constraints for string parameters, and parameter relationships not always explicit.

• Document complete output schemas for each tool. For example, list_instances returns {instances: [{id: int, name: string, host: string, port: int, enabled: bool, status: int, statusText: string, serverVersion: string}]}, make this explicit in a schema block or response documentation.
• Add enum constraints to string parameters. For get_aas_top_sql, define orderBy as enum: ['cpu', 'io', 'execCount']. For get_slow_sql, clarify sqlType as enum: ['rpc', 'batch'] if user-selectable.
• State numeric parameter bounds in descriptions. E.g., 'page: pagination page number (default 1, minimum 1)' and 'limit: rows per page (default 20, max 100 or server MaxRows config)'. Include the range in the description text, not just type.
• Clarify optional parameter relationships. For get_slow_sql and get_deadlocks: 'from and to are both optional; if one is specified, both should be. If both omitted, returns most recent data.'
• Enrich error messages with recovery guidance. Instead of returning {error: 'DbNotConfigured'}, return {error: 'Database not configured for instance 123. Ensure DBPilot:ConnectionString is set and the instance is enabled via list_instances.'}
• Add tool annotations for read-only semantics. Use [McpServerTool(readOnlyHint: true)] or equivalent to declare that all 11 tools are safe (no side effects, fully idempotent).
• Document chaining references. When get_slow_sql returns rowId, confirm that get_slow_sql_detail accepts the same rowId field name. Verify deadlock event IDs flow from get_deadlocks → get_deadlock_detail consistently.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry