DBA-Architect
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_migrationB | Audit SQL DDL statements, migration files, or migration directory against DBA best-practice rules (data types, unindexed FKs, locking DDL hazards, 1NF, alignment padding) for PostgreSQL or MySQL. |
| recommend_indexes_for_queriesB | Analyze raw SQL queries (including JOINs, CTEs, subqueries) using the ESR (Equality, Sort, Range) rule to recommend composite, covering, partial, and expression indexes, detect non-sargable predicates, and find redundant left-prefix indexes. |
| scan_project_queriesB | Statically scan a codebase directory to extract raw SQL and ORM/Query Builder patterns (Go, PHP/Laravel, TS/Prisma, Python), detect N+1 query loops, mask PII literals, and synthesize a holistic consolidated index plan per table. |
| analyze_explain_planB | Parse PostgreSQL or MySQL EXPLAIN / EXPLAIN (ANALYZE, BUFFERS) output (Text or JSON) to identify execution bottlenecks (Seq Scan, External Disk Sort, Heap Fetches, Row Misestimations) and generate a Mermaid plan flowchart. |
| plan_zero_downtime_migrationB | Transform blocking or hazardous DDL statements into a safe Multi-Phase Expand & Contract zero-downtime migration runbook for large production tables. |
| analyze_transaction_and_lockingB | Audit SQL or application transaction blocks to detect Lost Update race conditions (missing FOR UPDATE), external HTTP/network calls inside open transactions, and deadlock risks. |
| recommend_partitioning_and_archivingC | Design declarative table partitioning (RANGE, LIST, HASH), validate composite Primary Key constraints (PART-PK-001), and generate zero-bloat partition detach/drop retention runbooks. |
| calculate_db_capacity_and_configB | Estimate physical row size, heap/clustered table footprint, and B-Tree index memory requirements for N million rows, and generate tuned postgresql.conf or my.cnf parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit-migration | Audit SQL migration files for schema anti-patterns and generate a zero-downtime production rollout plan. |
| optimize-table-workload | Scan a project repository for all queries and transactions touching a specific table and build a consolidated index plan. |
| diagnose-slow-query-explain | Analyze an EXPLAIN ANALYZE output and SQL query to visualize bottlenecks in Mermaid and produce exact index fixes. |
| plan-production-rollout | Evaluate partitioning requirements, physical storage/RAM footprint, and database engine tuning for high-scale production rollout. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| DBA Architect Master Rule Catalog (30 Rules) | Complete catalog of all 30 deterministic DBA rules (SCHEMA-*, INDEX-*, CODE-*, EXPLAIN-*, TX-*, PART-*) with severity and remediation for PostgreSQL and MySQL. |
| ESR Column Cardinality Heuristics Dictionary | Heuristic column naming patterns and selectivity weights used for static ESR composite index ordering. |
| Zero-Downtime Migration Expand & Contract Templates | Production-safe online DDL templates for PostgreSQL (CONCURRENTLY, NOT VALID) and MySQL (ALGORITHM=INPLACE/INSTANT, gh-ost). |
TDQS
Scored across 8 tools
Most tools target clearly distinct artifacts: partitioning design, capacity math, DDL audit, index recommendation from raw SQL, codebase scanning, EXPLAIN parsing, zero-downtime transforms, and transaction auditing. The only close pairs are analyze_migration vs plan_zero_downtime_migration (audit vs transform) and recommend_indexes_for_queries vs scan_project_queries (input is raw SQL vs a codebase directory) — descriptions do disambiguate these, but an agent could still momentarily hesitate.
Every tool follows snake_case verb_noun structure (recommend_*, calculate_*, analyze_*, scan_*, plan_*), with action verbs leading the name consistently. Some names are long compound phrases but the convention is uniform throughout.
Eight tools is well within a healthy range and each covers a distinct, non-trivial DBA capability (partitioning, sizing, migration audit, indexing, codebase scan, EXPLAIN, zero-downtime, locking). No redundant or filler tools are present.
The surface covers the performance-and-schema-architecture lifecycle thoroughly — from query/index analysis through migration safety to partitioning and capacity planning. Notable gaps exist in operational areas like backup/restore, replication, vacuum/bloat monitoring, and role/permission management, though these may fall outside the server's stated design-audit scope.