MemoryBridge MCP Routines Server has 11 tools with complete input schemas and descriptions. Naming follows verb_noun convention (get_, create_, update_, mark_, approve_, reject_, list_). Descriptions are present (avg ~100 chars) but lack actionable context for LLM selection. Parameters are typed and mostly described, but lack constraints (enums, ranges, patterns). Output schemas are not documented. Error handling and recovery guidance are absent. Security-critical operations (approve_routine, create_routine_draft) lack confirmation/dry-run patterns. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear read/write distinction.

• Document output schemas for all 11 tools. Example for get_routine: {type: 'object', properties: {routine_id: {type: 'string'}, title: {type: 'string'}, status: {type: 'string', enum: ['draft','approved','active','completed']}, steps: {type: 'array', items: {type: 'string'}}, ...}, required: ['routine_id','title','status']}
• Add enum constraints to risk_level (low|medium|high|prohibited) and alert_type (help_requested|missed|other) parameters. Replace free-form strings with formal enums in schemas.
• Implement confirmation pattern for approve_routine and reject_routine. Add optional 'confirm' boolean parameter or return a 'requires_confirmation' response requiring a second call with confirmation_token.
• Add tool annotations: readOnlyHint=true for get_* and list_* tools; destructiveHint=true for approve_routine, reject_routine, mark_routine_status; idempotentHint=true for read-only tools.
• Enhance descriptions with recovery guidance. Example: 'Approve a routine draft. Enforces caregiver authorization. Returns 400 if routine not found (try get_routine to verify ID) or if already approved (idempotent). Returns 403 if caregiver lacks permission (contact admin).'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry