prospective-memory
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 |
|---|---|
| capture_taskA | Save a thought as an open task (same path as the Android capture box). |
| list_open_tasksB | List open tasks, newest first. Optional category: grocery, bills, people, inbox, … |
| search_tasksA | Search task text/category. By default only open items. |
| complete_taskB | Mark a task done. |
| drop_taskB | Drop a task without completing it. |
| task_statsB | Counts by status and open categories. |
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 6 tools
Each tool targets a distinct lifecycle action (capture, list, search, complete, drop, stats), so agents can generally tell them apart. The only mild overlap is that list_open_tasks and search_tasks can both retrieve open tasks by category, but search_tasks adds text matching to differentiate it.
Five of the six tools follow a clear verb_noun pattern: capture_task, list_open_tasks, search_tasks, complete_task, drop_task. task_stats breaks the pattern by using noun_noun, but this is a single minor deviation in an otherwise consistent set.
Six tools is well-scoped for a prospective-memory/task server. Each tool earns its place and there is no obvious redundancy or bloat.
The set covers the main task lifecycle: capture, list, search, complete, drop, and stats. The notable gap is the lack of an update/edit tool for changing task text or category, plus no explicit reopen flow, but these are workable gaps rather than fatal omissions.