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
Server capabilities have not been inspected yet.
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 |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: add_todo, get_todos, remove_todo, and update_todo_status handle CRUD operations for todos, while save_plan and start_planning manage the planning session lifecycle. The descriptions make it easy to differentiate between todo management and session control functions.
All tool names follow a consistent verb_noun pattern using snake_case, such as add_todo, get_todos, and save_plan. This uniformity makes the toolset predictable and easy to understand, with no deviations in naming conventions.
With 6 tools, the server is well-scoped for a software planning tool, covering todo management and session operations without being overly sparse or bloated. Each tool serves a clear purpose, making the count appropriate for the domain.
The toolset provides complete coverage for the software planning domain: start_planning initiates sessions, add_todo/get_todos/update_todo_status/remove_todo handle full todo lifecycle management, and save_plan allows persistence. There are no obvious gaps, enabling agents to perform all essential planning workflows.