Clean up your Django database effortlessly with customizable record removal based on your retention policy
Three tools with clear action verbs and structured schemas. Tool descriptions are present and describe state changes (destructive purge operation noted). Input schemas are properly typed with descriptions. However, output schemas are not documented in the source, parameter descriptions lack specificity around constraints, and error handling guidance is minimal. The server demonstrates solid foundational quality but lacks the rigor expected for A-grade tooling.
Execute a purge operation to delete records matching a retention policy. Requires a valid confirmation token from preview_purge.
List installed apps, models, and their date or datetime columns. Read-only. Use the returned (app_name, model_name, time_column) combinations as valid inputs to preview_purge.
Preview records that would be deleted under a retention policy without actually deleting them.
Output schemas are not documented. Tools return structured data (list_purge_candidates returns dict, preview_purge returns unknown structure, execute_purge returns unknown structure) but LLMs cannot plan downstream calls or extract fields without knowing the response shape.
Parameter constraints are missing or vague. 'retention_seconds' is documented as an integer but lacks range (positive, typical values). 'app_name', 'model_name', 'time_column' lack format hints or validation rules. This invites invalid inputs from LLMs.
Error handling lacks recovery guidance. The code raises PurgePolicyError with messages but tool descriptions do not guide LLMs on what to do when validation fails. No mention of 'try list_purge_candidates() first' or 'check DB_PURGE_MCP_ALLOWED_MODELS config'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2025-06-18+ | v2 |
Tool composition is not documented. preview_purge produces a confirmation_token for execute_purge, but this dependency is not made explicit in the descriptions. LLMs may not realize they must call preview first.
No idempotency or dry-run guarantees documented. execute_purge is destructive and requires a confirmation token, but the description does not guarantee the token prevents duplicate deletes if called twice, or explain token expiration behavior.