MCP Alchemy has 4 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (positive), but they are verbose and include dynamic database connection info that clutters the core purpose. Parameter descriptions are minimal or absent. The execute_query tool accepts arbitrary SQL with only a 'query' string parameter, no validation, no enum constraints, no guidance on safe vs. unsafe operations. Schema definitions are present but sparse (only type and description for most params). No error handling guidance, no recovery hints, and no tool annotations (readOnlyHint/destructiveHint). The server uses FastMCP (good) but STDIO transport caps protocol readiness at 50.

• Remove database connection metadata from tool descriptions. Move to a separate 'connection_info' resource or log it at startup. Descriptions should be: 'all_table_names: List all table names in the connected database.' (20 chars, clear, LLM-optimized).
• Add parameter descriptions to schema_definitions (table_names: 'Array of table names to retrieve schema for. E.g. ["users", "orders"]') and execute_query (params: 'Optional dict of named parameters for parameterized queries. Keys are param names, values are strings/numbers/booleans.').
• Wrap execute_query in a safety layer: validate query against a whitelist of allowed patterns (SELECT, DESCRIBE, SHOW) or require explicit 'allow_write=true' flag. Return 'Destructive query detected. Pass allow_write=true to confirm.' for INSERT/UPDATE/DELETE.
• Add tool annotations: readOnlyHint=true for all_table_names, filter_table_names, schema_definitions; destructiveHint=true for execute_query when it detects INSERT/UPDATE/DELETE.
• Improve error messages: catch SQL syntax errors and return 'SQL syntax error at position X. Check query for typos. Common issues: missing quotes, invalid column names.' For permission errors: 'Access denied. Verify user has SELECT privilege on the target table.'