No user-submitted related servers found.
Scored across 25 tools
Each tool has a clearly distinct purpose: read-only queries, preview dry-runs, and apply mutations are separated with explicit _preview and _apply suffixes. Resource-specific operations (todo, time, file, db, diagnose) are well compartmentalized, leaving no ambiguity between tools.
Most tools follow a resource_action or resource_action_preview/apply pattern in snake_case (e.g., todo_list, todo_create_apply, db_export). However, a few outliers like safety_policy, report_daily, report_weekly, diagnose_report, and diagnose_collect deviate from the verb_noun convention, making the set slightly inconsistent.
At 25 tools, the server covers multiple domains (todos, time logging, reports, diagnostics, file management, DB import/export), which explains the large count. While each tool serves a purpose, the set feels heavy and may overwhelm agents; it sits at the top of the 'borderline' range for tool count.
The tool surface covers core workflows: todo lifecycle (create, update, transition, list, get), time logging, daily/weekly reports, file operations, diagnostics, and DB import/export. Minor gaps exist, such as no update/delete for time logs, no explicit todo delete (though archived status may suffice), and diagnostic suggestions are not executable within the server.