Read-only MCP server that inspects a Postgres database and its paired git repo: schema, ERD, missing indexes, circular FKs, migration risk, table complexity, and git-churn hotspots.
Schema-sentinel has 8 well-named, read-only tools with clear descriptions (avg 85 chars, all >20 chars). However, 6 of 8 tools have EMPTY input schemas ({}), violating the critical rule that tools with no input schema must score 0 on schema. Only check_migration_risk and find_schema_churn/generate_report have documented parameters. Parameter descriptions are present where schemas exist. No error handling guidance, no output schema documentation, no tool annotations. STDIO transport caps protocol readiness at 50.
Statically parses a single migration .sql file and flags risky patterns. Never executes it.
Catches FK cycles across tables.
Flags FK columns with no covering index.
Git-history churn per table: how often (and how recently) each table's migrations changed.
Structural complexity per table: column count, FK fan-in/out, circular-FK involvement.
Mermaid erDiagram text for the connected schema.
Rolls every tool above into one combined health report.
6 of 8 tools have empty input schemas ({}). This violates pattern:constrained-input and pattern:tool-description.
No output schema documentation. LLMs cannot plan downstream calls or extract fields without knowing return structure. get_schema_overview returns dict, find_missing_indexes returns list[dict], but field names and types are undocumented.
No error handling guidance. Tools that query a database or git repo can fail (connection errors, missing migrations path, invalid SQL syntax) but provide no recovery hints. Violates pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Tables, columns, PKs, FKs for the connected database.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All 8 tools are read-only and idempotent, annotating them would help agents reason about safety and retry logic.
Parameters 'since_days' in find_schema_churn and generate_report lack min/max bounds. Unbounded integers let LLMs pass absurd values (negative days, year 9999). Should specify range (e.g., 1 - 365).