MCP server for Life OS - a personal operating system for managing tasks, pages, notes, finances, and databases with OAuth 2.0 authentication
Critical failures across all 20 tools. No input schemas visible in provided source code, cannot verify parameter types, constraints, or descriptions. Tool definitions appear to be registered via mcp-handler framework (src/lib/mcp/tools/index.ts calls registerTaskTools, registerPageTools, etc.), but actual schema definitions are not shown. Helper functions (withUser, withLogging, errorResult, jsonResult) show basic error handling and structured output support, but tool-level descriptions and parameter documentation are not evident. The 20 tools follow a consistent CRUD pattern (create/list/update/delete for tasks, pages, notes, finance, databases) which is good for naming clarity, but without visible schema definitions, descriptions, and parameter constraints, quality cannot be verified.
No input schemas visible in source code. Tool definitions registered via mcp-handler framework but actual schema files (src/lib/mcp/tools/tasks.ts, pages.ts, notes.ts, finance.ts, databases.ts) not provided. Cannot verify parameter types, constraints, or descriptions.
No tool descriptions visible in provided source. Tool registration code (src/lib/mcp/tools/index.ts) only shows function calls to registerTaskTools, registerPageTools, etc., but actual description strings are not shown.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2025-06-18+ | v2 |
Tool definitions inferred from file paths and function names, not directly visible in source. Actual registration code in tasks.ts, pages.ts, notes.ts, finance.ts, databases.ts not provided.
No parameter descriptions visible. Even if schemas exist in unshown files, descriptions for individual parameters (e.g., what does 'title' mean for task_create? What format for 'due_date'?) are not evident in provided code.
No output schema documentation visible. Helper functions (jsonResult, errorResult) show structured output support, but what fields does task_list return? What does page_create return? Not documented in provided source.