Scored across 191 tools
The surface contains many overlapping clusters: run_select / run_analytical_query / run_select_tuned / run_select_parallel, explain_query / analyze_query_plan / why_is_this_slow / optimize_query, and numerous recommend_* / audit_* / status-probe tools. Descriptions are detailed and often cross-reference each other, but with 191 tools the boundaries are still hard for an agent to hold reliably, leading to likely misselection.
All tool names use snake_case and the dominant pattern is verb_noun (list_tables, describe_table, recommend_indexes, get_server_info). There are minor noun-first deviations such as vector_search, hybrid_search, and pg_search_run, but the overall convention remains readable and mostly consistent.
191 tools is an extreme mismatch for a single MCP server surface, even for a broad PostgreSQL administration product. The catalogue should be split into focused servers or packs; as one set, discovery and selection cost is overwhelming and each tool no longer clearly earns its place.
The read-only introspection, advisor, and diagnostics surface is extremely deep, but core lifecycle operations are absent: there are no write/DDL/transaction tools. Multiple descriptions explicitly point agents to run_write, prepare_migration, validate_migration_schema, alter_system, run_maintenance, and list_tools, none of which appear in this catalogue, creating dead ends.
