powerplan
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_iterationA | JSON for the current iteration (what to work on now). Preferred agent entry — avoids reading all of PLAN.md. |
| get_iterationC | JSON for one iteration by version (goal, tasks, progress). |
| list_iterationsB | List iterations filtered by open | complete | all. |
| find_taskC | Locate tasks by substring match (JSON). |
| get_backlogC | Backlog section items (JSON). |
| show_current_iterationA | ASCII view of the resolved current iteration (humans/logs). |
| show_planA | Compact index: counts + current iteration. Agents should prefer get_current_iteration / get_iteration over this or full PLAN.md. |
| check_planC | Structure lint: duplicates, multiple current, complete-with-open-tasks. |
| create_planA | Bootstrap a new PLAN.md when none exists (powernote-style skeleton). Default path: ./PLAN.md in cwd. Refuses overwrite unless force=true. |
| create_majorC | Create ## vX.Y — Title major section. |
| create_iterationD | Create ### vX.Y.Z — Title iteration. |
| set_iteration_goalC | Set/replace Goal: on an iteration. |
| add_taskC | Append a checkbox task to an iteration. |
| add_tasksA | Append several checkbox tasks in one write. Prefer this over repeated add_task. Shared done/agent apply to every item. |
| complete_taskA | Tick one or many tasks in one write. For several, pass indexes (preferred after get_iteration) or tasks. For exactly one, index or task still work. |
| reopen_taskA | Untick one or many tasks in one write. For several, pass indexes or tasks. For exactly one, index or task still work. |
| update_taskB | Rewrite task text, preserving done state. One task: text + index/task. Several: changes[{text, index|task, expect?}]. |
| remove_taskA | Delete one or many tasks in one write. For several, pass indexes or tasks. Resolve-all then drop (indexes do not shift). |
| defer_taskA | Move one or many tasks to the backlog in one write. For several, pass indexes or tasks. Shared reason/agent apply to every item. |
| add_to_backlogB | Append one (text) or many (texts) items to Future (Backlog) in one write. |
| append_proseC | Append freeform markdown at top level. |
| start_iterationA | Mark iteration ACTIVE / current; clears other current markers. |
| close_iterationB | Mark iteration COMPLETE. Requires force=true if open tasks remain. Optional stamp (e.g. date) appended to title. |
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 23 tools
Most tools have clear resource+action boundaries, but get_current_iteration vs show_current_iteration are close in purpose, and add_task vs add_tasks overlap. The descriptions do clarify JSON vs ASCII and single vs batch, so confusion is limited.
All tool names consistently follow a lowercase snake_case verb_noun pattern, with verbs like get, list, create, update, add, complete, reopen, remove, defer, start, and close. The naming style is uniform and predictable.
23 tools is on the heavy side for a plan-management utility. Many serve specific operations, but several near-duplicates like add_task/add_tasks and get_current_iteration/show_current_iteration suggest the surface could be tightened.
The core plan, iteration, task, and backlog lifecycle is well covered: create, query, update, complete, reopen, remove, defer, start, and close. Minor gaps remain, such as no remove iteration, remove major, or explicit backlog item removal, but they are workaroundable.