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
Every tool has a clearly distinct purpose with no ambiguity. The tools cover specific actions like adding, getting, removing, updating status, saving, and starting planning, each targeting a unique operation in the planning workflow.
All tool names follow a consistent verb_noun pattern (e.g., add_todo, get_todos, remove_todo). The naming is uniform and predictable, using snake_case throughout without any deviations.
With 6 tools, the count is well-scoped for a software planning domain. Each tool earns its place by covering essential CRUD operations and session management, avoiding bloat or thinness.
The tool set provides complete CRUD/lifecycle coverage for todo management (add, get, remove, update status) and includes session operations (start planning, save plan). There are no obvious gaps for the stated purpose of software planning.