Schema Sentinel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCHEMA_SENTINEL_DB_URL | Yes | Postgres connection string for a read-only role | |
| SCHEMA_SENTINEL_REPO_PATH | Yes | Path to the git repository paired with the database | |
| SCHEMA_SENTINEL_MIGRATIONS_PATH | Yes | Path to the migrations directory |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_schema_overviewB | Tables, columns, PKs, FKs for the connected database. |
| find_missing_indexesA | Flags FK columns with no covering index. |
| find_circular_foreign_keysA | Catches FK cycles across tables. |
| find_table_complexityA | Structural complexity per table: column count, FK fan-in/out, circular-FK involvement. |
| generate_erdB | Mermaid erDiagram text for the connected schema. |
| check_migration_riskA | Statically parses a single migration .sql file and flags risky patterns. Never executes it. |
| find_schema_churnB | Git-history churn per table: how often (and how recently) each table's migrations changed. |
| generate_reportC | Rolls every tool above into one combined health report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct analytical concern: index coverage, FK cycles, table complexity, ERD generation, migration risk, schema churn, combined reporting, and schema overview. There is no meaningful overlap between tool purposes.
All tool names follow a consistent verb-first snake_case pattern (e.g., find_missing_indexes, generate_erd). The verbs are imperative and the object is clear, making the set predictable.
Eight tools is well-scoped for a schema health analysis server. Each tool earns its place and covers a specific aspect of schema inspection without bloat.
The toolset covers a broad range of schema health checks: current schema, migrations, history, and ERD generation. Minor gaps exist such as index performance analysis or orphaned FK detection, but the core workflows are solid.