A small MCP server showing explicit tool boundaries, least-privilege scopes, confirmations, and safe audit logs.
Strong foundation with explicit tool boundaries, least-privilege scopes, and comprehensive audit logging. All 4 tools have descriptions (10-120 chars), input schemas with types, and tool annotations (readOnlyHint, destructiveHint, idempotentHint). Zod validation enforces parameter constraints (UUID format, string length limits). Destructive operations require confirmation. However, output schemas are not formally documented, responses are wrapped in generic {content, structuredContent} without explicit field definitions. Parameter descriptions are minimal (1-2 sentences); LLM-optimized descriptions should explain WHEN to use each tool and dependencies. Error messages are generic; recovery guidance is absent.
Create a local note. Requires the notes:write scope.
Delete a note. Requires notes:admin and confirmation exactly matching "DELETE <id>".
Read one note by its opaque identifier.
List note metadata without returning note bodies.
Output schemas not formally documented. Responses wrapped in generic {content, structuredContent} structure without explicit field definitions for note objects (id, title, body, revision, createdAt, updatedAt). LLMs cannot plan downstream calls or extract fields reliably.
Error messages lack recovery guidance. PermissionDenied and NoteNotFound errors are thrown but do not suggest next steps (e.g., 'Try calling notes.list() to see available notes' for NoteNotFound). Agents cannot self-correct.
Parameter descriptions are minimal. 'The note identifier' and 'Confirmation string matching DELETE <id>' lack context on format, constraints, or when to use. Descriptions should be 50-200 chars and explain WHAT, WHEN, and WHY.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2025-06-18+ | v2 |
notes.list() returns metadata without pagination support. No limit, offset, or cursor parameters. If notes grow large, response bloat will exhaust context windows. Baseline: 20-50 items per page.
Confirmation mechanism for notes.delete is fragile. Requires exact string match 'DELETE <id>' but does not validate that the id parameter matches the confirmation string. Typos or mismatches silently fail without clear error.