Software Planning Tool
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_planningB | Start a new planning session with a goal |
| save_planC | Save the current implementation plan |
| add_todoB | Add a new todo item to the current plan |
| remove_todoA | Remove a todo item from the current plan |
| get_todosA | Get all todos in the current plan |
| update_todo_statusB | Update the completion status of a todo item |
| update_goalA | Update the description of the current goal |
| get_planA | Get the current implementation plan as formatted text |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Goal | The current software development goal being planned |
| Implementation Plan | The current implementation plan with todos |
TDQS
Scored across 8 tools
Each tool targets a distinct action: session management (start, save), goal editing, todo CRUD (add, remove, get, update status), and plan retrieval. There is no ambiguity about which tool to use for a given operation.
All tool names follow a consistent verb_noun pattern in snake_case (start_planning, add_todo, update_goal). The verbs are clear and predictable, with only minor gerund deviation in start_planning that does not hinder readability.
Eight tools is well-scoped for a planning session domain, covering lifecycle operations without redundancy or bloat. Each tool earns its place in the set.
The surface covers the full planning lifecycle: creating a session, saving, updating the goal, managing todos (add, remove, update status), and retrieving the plan. There are no obvious missing operations for the intended purpose.