agent-gantt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_GANTT_DB | No | Path to the SQLite database used to store project plans. Defaults to ~/.local/state/agent-gantt/projects.sqlite3. Set this to share a database across clients or choose another durable location. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_projectD | Create project. |
| create_taskC | Create task. summary: few words for humans; description: agent detail. parent_task_id groups subtasks, not a dependency. |
| update_taskC | Update supplied fields; null clears a date. Claimed tasks require actor=owner. |
| add_dependencyC | Add predecessor; rejects cycles and cross-project edges. |
| list_projectsC | List project IDs/names; detail on demand. |
| project_viewC | Paginated snapshot. Save revision. ready_only finds executable tasks; assignee includes unassigned when ready_only. |
| coordinateC | Atomic task lifecycle with fresh revision. Claim checks assignment/dependencies. Owner can block/resume/report progress/release/complete; reason records evidence. |
| changesD | Read unfiltered task changes after_revision. Apply by task ID; after all pages poll from through_revision. Get full task using event revision. |
| batchB | Atomic 1..50 task/dependency operations. Each has tool, arguments, optional ref on create_task. Use $ref in later task_id/depends_on_id. |
| get_detailC | Retrieve complete JSON in segments; concatenate json_segment using next_offset. For stable task reads use kind=event and revision as id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
There is real overlap between mutation tools (update_task vs coordinate, which both change task state/lifecycle) and among read tools (list_projects, project_view, changes, get_detail all surface state). Descriptions help distinguish them (snapshot vs. delta vs. raw JSON), but an agent must read carefully to choose the right read/write path.
Mostly verb_noun (create_project, create_task, update_task, add_dependency, list_projects), but the set mixes in bare verbs (coordinate, changes, batch) and a noun_verb (project_view). Readable, but not a predictable single pattern.
10 tools is well-scoped for a Gantt/project-management server, covering project, task, dependency, lifecycle, batch, and read/sync operations without bloat.
Create/update exist for tasks and create/list for projects, but there is no delete_task, delete/update_project, or remove_dependency (add_dependency has no inverse). Read/sync coverage is strong, but lifecycle gaps could force agents into workarounds.