Skip to main content
Glama

Related Servers

Alternatives to lilt-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource+action (create/update/delete/complete/reopen/snooze/unsnooze on tasks, list/log on habits, list on projects). The only mild friction is that update_task's allowed fields are unspecified, so an agent might wonder whether status changes belong there rather than in complete_task/reopen_task. Snooze/unsnooze are explicitly delineated as out-of-band from update_task, which keeps the boundaries largely clear.

    Naming Consistency5/5

    Every tool follows the same snake_case verb_noun pattern (list_projects, create_task, log_habit, unsnooze_task). Verb choice is also semantically consistent, with paired opposites (snooze/unsnooze, complete/reopen) named symmetrically.

    Tool Count5/5

    Eleven tools is well within a comfortable range for a task/habit client. Each tool covers a genuinely distinct operation — the task lifecycle alone justifies seven of them, and no tool looks redundant or vestigial.

    Completeness3/5

    The task surface is essentially complete (create, list, update, delete, complete, reopen, snooze, unsnooze). However, habits only have list and log — there is no way to create, edit, or archive a habit — and projects are read-only, so agents will hit dead ends outside the task domain. Workarounds exist (habits/projects presumably managed in the Lilt app), but the surface is uneven.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data