todo-full
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | 添加一条待办任务。 |
| complete_taskA | 把指定 id 的任务标记为完成。 |
| delete_taskA | 删除指定 id 的任务。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_review | 生成一段"回顾今天待办"的提示词。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_todos | 全部任务（只读快照）。 |
TDQS
Scored across 3 tools
Each tool targets a distinct action on a task: adding, completing, or deleting. There is no overlap or ambiguity between them.
All tools follow the same verb_noun pattern: add_task, complete_task, delete_task. Naming is uniform and predictable.
With only 3 tools, the set is minimal but each tool serves a clear purpose in the todo domain. The count is well-scoped and appropriate.
The set includes create, complete, and delete operations but lacks a way to list or retrieve tasks. This is a significant gap since agents cannot view existing tasks, making the tool surface incomplete for a todo workflow.