Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
authenticate_userC

Authenticate user with Apple ID to access their addTaskManager data

assess_create_taskC

Create a new task in Assess realm (content editing, no contexts/dates).

assess_edit_taskC

Edit task content in Assess realm (taskName, priority).

assess_create_projectC

Create a new project in Assess realm.

assess_create_ideaB

Capture a new idea (always starts in Assess realm).

assess_create_collectionC

Create a new collection in Assess realm.

assess_create_contextC

Create a new context in Assess realm.

assess_edit_projectC

Edit project content in Assess realm.

assess_edit_ideaC

Edit idea content in Assess realm.

assess_add_task_to_projectC

Add an existing task to a project in Assess realm.

assess_add_task_to_ideaC

Add an existing task to an idea in Assess realm.

assess_remove_task_from_projectC

Remove a task from a project in Assess realm.

assess_remove_task_from_ideaC

Remove a task from an idea in Assess realm.

assess_archive_task_to_collectionC

Archive a task to a collection.

assess_archive_project_to_collectionC

Archive a project to a collection.

decide_assign_contextC

Assign contexts to tasks/projects in Decide realm.

decide_set_project_intervalC

Set project interval (start date and end date) in Decide realm.

decide_set_task_due_dateC

Set due date for a task in Decide realm.

decide_set_task_alertC

Set task alerts in Decide realm.

decide_move_task_to_doC

Move task to Do realm from Decide realm.

decide_move_task_to_assess_from_decideC

Move task to Assess realm from Decide realm.

decide_move_project_to_doC

Move project to Do realm from Decide realm.

decide_move_project_to_assess_from_decideC

Move project to Assess realm from Decide realm.

do_mark_task_as_doneC

Mark tasks as completed in Do realm.

do_mark_project_as_doneC

Mark projects as completed in Do realm.

get_tasks_by_realmC

Filter tasks by realm.

get_projects_by_realmC

Filter projects by realm.

get_ideasC

Get all ideas.

moveToRealmC

Move a task or project to a specific realm.

get_collectionsB

Get all collections.

get_tasks_by_contextC

Filter by context.

get_stalled_items_in_decideB

Find stalled items (tasks + projects) in Decide realm.

get_undecided_items_in_decideB

Find undecided items (tasks + projects) in Decide realm.

get_ready_items_in_decideB

Find ready to do items (tasks + projects) in Decide realm.

get_tasks_today_in_doB

Find tasks due today in Do realm.

get_tasks_tomorrow_in_doA

Find tasks due tomorrow in Do realm.

get_tasks_soon_in_doB

Find tasks due soon in Do realm.

get_tasks_overdue_in_doB

Find tasks overdue in Do realm.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 38 tools

Disambiguation3/5

The tools have clear purposes within their realms (Assess, Decide, Do) and operations (create, edit, move, get), but there is significant overlap in functionality across realms. For example, multiple 'move' tools exist for tasks and projects between realms, and many 'get' tools filter by similar criteria (realm, context, date), which could cause confusion about which to use for specific queries.

Naming Consistency4/5

Most tools follow a consistent snake_case pattern with a clear structure: realm_verb_noun or verb_noun_in_realm. However, there are minor deviations like 'authenticate_user' (no realm prefix) and 'moveToRealm' (camelCase, inconsistent with others), which slightly disrupt the overall consistency.

Tool Count2/5

With 38 tools, the count is excessive for a task management server, leading to potential bloat and confusion. Many tools could be consolidated (e.g., multiple 'get' filters into one with parameters), and the high number suggests over-specialization rather than a well-scoped set, making it heavy for agents to navigate.

Completeness5/5

The tool set provides comprehensive coverage for task management across Assess, Decide, and Do realms, including CRUD operations (create, edit, get), lifecycle management (move, archive, mark as done), and filtering by various criteria (realm, context, date). No obvious gaps are present; agents can handle full workflows from idea capture to completion.

Maintenance

ActivityInactive
ResponsivenessNo issues