This server exposes 43 tools for Things 3 task management with a STDIO-only transport. Tool names follow verb_noun conventions (get_todos, add_todo, etc.), which is good. However, descriptions are inconsistent in quality: some provide context (e.g., get_todos mentions 'AppleScript for projects'), while others are terse (e.g., get_projects 'Get all projects directly from database' lacks guidance on when to use it vs. get_areas). Parameter descriptions exist for most tools but lack granularity, many params like 'kwargs' (in add_todo, update_todo, add_project, update_project, add_area, update_area) are documented as 'Optional parameters like project, area, tags, due date, etc.' without enumerating valid keys, constraints, or format guidance. No tool explicitly declares output schemas, making it unclear what fields an LLM should expect. Error handling is not documented, no guidance on retryability, user-fixability, or recovery paths. Destructive tools (delete_todo, bulk_delete_todos) lack dry-run/confirmation patterns. Security consideration: tools accept direct IDs without validation or injection guards mentioned. The 'kwargs' pattern is a red flag, it obscures required vs. optional fields and invites LLMs to hallucinate parameters. Overall, the server is functional but lacks the precision and guardrails expected of production agent tools.

• Replace all 'kwargs' object parameters with explicit, enumerated parameter sets. Document which keys are valid, required, and what formats they accept. E.g., add_todo should declare: title (required, string), project_uuid (optional, string, UUID format), due_date (optional, ISO 8601 date), tags (optional, array of strings), area_uuid (optional, string, UUID format).
• Document output schemas for all tools. Specify what fields are returned, their types, and which are guaranteed to be present. E.g., get_todos returns [{id: string, title: string, due_date: string|null, project_uuid: string|null, completed: boolean}, ...]. This enables LLMs to chain operations.
• Add dry-run or confirmation flow for destructive operations. delete_todo and bulk_delete_todos should support a 'confirm=true' parameter or return a confirmation_required response that requires explicit user approval before proceeding.
• Consolidate duplicate tools. Merge get_due_in_days and get_todos_due_in_days into a single canonical tool with clear name (e.g., get_todos_due_in_days). Remove the redundant get_due_in_days. Same for get_activating_in_days / get_todos_activating_in_days.
• Add tool annotations to expose risk classification. Use readOnlyHint=true for all get_* tools, destructiveHint=true for delete_* tools, and idempotentHint=true for tools that can be safely retried. This enables LLM-driven safety reasoning.
• Document error responses with actionable recovery paths. E.g., 'Todo not found (UUID: abc123). Try search_todos() first to locate the item, or list recent items with get_today().'

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

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