Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
POSTGRES_URLNoPostgreSQL connection URL (when DATA_STORE_TYPE=postgresql). Format: postgresql://user:password@host:port/database
DATA_STORE_TYPENoStorage backend type. Options: 'filesystem' or 'postgresql'filesystem
FILESYSTEM_PATHNoPath to filesystem storage directory (when DATA_STORE_TYPE=filesystem)/tmp/tasks
MULTI_AGENT_ENVIRONMENT_BEHAVIORNoControls how tasks appear in 'ready tasks' queries. 'false' (default): both NOT_STARTED and IN_PROGRESS tasks are ready. 'true': only NOT_STARTED tasks are ready (prevents multiple agents from working on same task)false

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsB

List all projects in the task management system, including default projects (Chore and Repeatable)

create_projectC

Create a new project with a name and optional agent instructions template

get_projectC

Retrieve a project by its ID or name

update_projectB

Update an existing project's name and/or agent instructions template

delete_projectA

Delete a project and all its task lists and tasks. Default projects (Chore, Repeatable) cannot be deleted.

get_task_listB

Retrieve a task list by its ID, including all its tasks

create_task_listA

Create a new task list with project assignment logic. If repeatable=true, assigns to 'Repeatable' project. If no project specified, assigns to 'Chore' project. Otherwise assigns to specified project (creating it if needed).

delete_task_listC

Delete a task list and all its tasks

create_taskC

Create a new task with all required fields (title, description, status, dependencies, exit_criteria, priority, notes) and optional fields (research_notes, action_plan, execution_notes, agent_instructions_template, tags)

get_agent_instructionsB

Generate agent instructions for a task using template resolution hierarchy (task → task list → project → fallback)

update_task_dependenciesC

Update task dependencies with circular dependency validation

add_task_noteC

Add a general note to a task

add_research_noteC

Add a research note to a task

update_action_planC

Update the action plan for a task (replaces existing action plan)

add_execution_noteC

Add an execution note to a task

update_exit_criteriaC

Update exit criteria for a task, marking individual criteria as COMPLETE or INCOMPLETE

update_task_statusA

Update task status with exit criteria validation (cannot mark COMPLETED unless all exit criteria are COMPLETE)

get_ready_tasksB

Retrieve tasks that are ready for execution (tasks with no pending dependencies or all dependencies completed) within a specified scope (project or task list)

add_task_tagsC

Add tags to a task with validation and deduplication. Tags are labels for categorization and filtering.

remove_task_tagsA

Remove tags from a task. Tags that don't exist on the task are silently ignored.

search_tasksB

Search and filter tasks by multiple criteria including text query, status, priority, tags, and project. Supports pagination and sorting.

analyze_dependenciesB

Analyze task dependencies within a scope (project or task list). Returns critical path, bottlenecks, leaf tasks, progress, and circular dependencies.

visualize_dependenciesB

Generate a visualization of task dependencies within a scope (project or task list). Supports ASCII art, Graphviz DOT format, and Mermaid diagram formats.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 23 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific resources and actions, such as create_task vs. update_task_status. However, there is some overlap among the note-adding tools (add_execution_note, add_research_note, add_task_note), which could cause confusion as their differences are subtle and not clearly differentiated in descriptions.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as create_project, delete_task_list, and update_action_plan. All tools use snake_case with clear, descriptive verbs, making the naming predictable and easy to understand.

Tool Count3/5

With 23 tools, the count is borderline high for a task management server, potentially feeling heavy and overwhelming. While it covers many operations, it may include tools that could be consolidated or simplified, such as multiple note-adding functions, leading to some redundancy.

Completeness5/5

The tool set provides comprehensive CRUD and lifecycle coverage for tasks, projects, and task lists, including creation, retrieval, updating, deletion, dependency analysis, visualization, and search. There are no obvious gaps; all core operations for task management are well-covered, ensuring agents can handle full workflows without dead ends.

Maintenance

ActivityStale
ResponsivenessNo issues