Skip to main content
Glama

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_createB

Create a new project. Projects are the top-level container for all work.

project_listA

List all projects with epic/task counts and completion percentages. Optionally filter by status.

project_updateA

Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.

epic_createA

Create an epic within a project. Epics group related tasks into a feature or workstream.

epic_listA

List epics for a project with task counts and completion stats. Filter by status, priority or branch. Archived epics are hidden unless include_archived is set.

epic_archiveA

Archive or unarchive an epic. Archived epics and their tasks drop out of listings, the dashboard and search unless include_archived is set. For putting finished work out of sight without cancelling it; nothing is deleted.

epic_updateA

Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete. Pass branch="current" to pin to the active branch, or empty string to clear.

task_createA

Create a task within an epic. Tasks are the primary unit of work.

task_listA

List tasks; without epic_id, across all epics. Includes subtask and dependency counts. Rows are compact: nulls and metadata dropped, descriptions cut to 120 chars (task_get for full). branch="current" restricts to the active git branch.

task_reorderA

Set the order of an epic's tasks. Omitted IDs keep their relative order at the end. task_list then follows this arrangement by default.

task_deleteA

Remove a task (soft delete). Only 'todo' tasks — anything further along has history worth keeping. The row is kept and hidden from listings; task_restore brings it back.

task_restoreA

Restore a task removed with task_delete.

task_lock_descriptionA

Lock or unlock a task's description. While locked, task_update refuses to change it — a guard against rewriting the spec when you meant to add a comment. Every other field still changes freely.

task_getA

Get a single task with full details including all subtasks, related notes, comments, and dependencies.

task_updateA

Update a task; pass only fields to change. Completing it while subtasks are unfinished is refused unless force is set.

subtask_createA

Create subtasks (checklist items) for a task. Pass titles as an array — one string per subtask — and each becomes its own record. New subtasks are appended after any that exist.

subtask_updateA

Update a subtask title, status or position. depends_on sets what it waits on, blocks the inverse; both replace the set, [] clears. Starting or finishing one with unmet prerequisites needs force.

subtask_reorderA

Reorder a task subtask list. Pass IDs in the order you want; any omitted keep their relative order at the end.

subtask_deleteC

Delete one or more subtasks. Accepts a single ID or array of IDs.

note_saveA

Create or update a note: decisions, context, progress, meetings, blockers, technical detail, releases. With id, updates; without, creates.

note_listB

List notes with optional filters. Returns notes sorted by most recent first.

note_searchB

Search across note titles and content by keyword.

note_deleteA

Delete a note by ID.

comment_addA

Add a comment to a task. Comments create a chronological discussion thread — useful for leaving breadcrumbs across sessions.

comment_listA

List comments on a task in chronological order. Comments removed with comment_delete are hidden by default; pass include_deleted to see them with their removal reason.

comment_deleteA

Remove a comment (soft delete). The row is kept for the audit trail but hidden from comment_list and task_get. Use this to retract a comment that turned out to be wrong or stale. Reversible with comment_restore.

comment_restoreA

Restore a comment previously removed with comment_delete.

template_createA

Create a reusable set of tasks that can be instantiated into any epic. {variable} placeholders are filled in on apply.

template_listA

List task templates. Pass include_tasks to see what each one actually creates.

template_applyA

Apply a template to create tasks in an epic. Replaces {variable} placeholders with provided values.

template_updateA

Edit a template in place. Only the fields you pass change; tasks replace the whole list.

template_deleteA

Delete a task template.

tracker_dashboardA

Full project overview in one call: project, epics with task counts, stats, blocked and overdue tasks, recent activity and notes. Best first call when starting work. branch="current" scopes to the active git branch.

tracker_initA

Initialize the tracker for a project. If the database is empty, creates a project with the given name. If a project already exists, returns its info.

tracker_searchA

Search projects, epics, tasks and notes by keyword. Returns categorized previews — use task_get or note_list for full text.

tracker_nextA

What to work on next: one recommended task with the reason, its next unfinished subtask, alternatives, and — when nothing is actionable — what to unblock. Call it when resuming work; cheaper than tracker_dashboard.

activity_logA

View the activity log showing what changed and when. Useful for understanding recent progress or reviewing what happened since the last session.

tracker_session_diffA

What changed since a timestamp: counts by action and entity, plus the notable changes. Call it at the start of a session to catch up.

task_batch_updateA

Update multiple tasks at once. Useful for changing status of several tasks (e.g., mark 3 tasks as done) or reassigning tasks.

tracker_exportA

Export a full project as nested JSON. Includes all epics, tasks, subtasks, comments, dependencies, and related notes. Useful for backup, migration, or sharing.

tracker_importA

Import a project from JSON (matching tracker_export format). Creates all entities with new IDs and remaps references. Uses a transaction for atomicity.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 41 tools

Disambiguation3/5

Most tools have distinct resource-action pairs (task_create vs epic_create), but some overlap: tracker_init initializes a project while project_create creates one; tracker_dashboard, tracker_session_diff, and activity_log all provide overview/activity info, though with different scopes. Also task_get vs task_list vs tracker_search could create some selection ambiguity.

Naming Consistency4/5

Most tools follow a consistent noun_verb pattern (e.g., task_create, task_update, epic_list, note_save). Exceptions like note_save (verb_noun) and activity_log (noun_noun) break the pattern, and tracker_* and template_* prefixes are mixed but still readable.

Tool Count2/5

41 tools is excessive for a project management server, even with comprehensive functionality. Many tools could be consolidated (e.g., note_save could be split into create/update, or tracker_export/import are edge-case features). This is well beyond the typical 3-15 tool sweet spot and creates cognitive load.

Completeness5/5

The tool surface is remarkably complete: full lifecycle for projects, epics, tasks, subtasks, notes, comments, and templates. Includes reordering, soft-delete with restore, batch operations, search, dashboard, diff, and import/export. There are no obvious dead ends; every entity has create/read/update/delete plus additional utilities.

Maintenance

ActivityMaintained
ResponsivenessResponsive