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. Includes live JARVIS notification counts. |
| latest_otpA | Newest OTP from the phone (SMS/bank/mail/WhatsApp notification). Expires in ~3 minutes. If redacted=true, Android hid the digits — tell the user to look at the phone. Never invent a code. |
| last_whatsappA | Recent WhatsApp notification previews from the phone. Optional sender name filter (e.g. Mom). This is the notification shade, not full chat history. |
| missed_summaryA | What arrived on the phone recently: WhatsApp, mail, SMS, OTPs (codes not included). Default last 60 minutes. |
| list_remindersB | List reminders from the unified Remy Reminders ledger (pending, snoozed, completed). |
| create_reminderC | Create a new reminder in the unified ledger. If armed=false, creates an unarmed inbox item. |
| capture_cultural_itemB | Capture a cultural or leisure recommendation (movie, show, documentary, book) into the ledger. |
| list_cultural_itemsC | List movie and cultural recommendations queued in the leisure ledger. |
| snooze_reminderC | Snooze a reminder to a target ISO date/time or by N minutes. |
| complete_reminderC | Mark a reminder completed in the unified ledger. |
| resolve_music_queryA | Resolve a natural language music query (e.g. 'play spb songs hindi', 'play lofi') to stream metadata. |
| play_musicB | Start zero context-switch background music playback for a query (e.g. 'play spb songs hindi', 'play lofi'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekend_watchlist_prompt | Prompt for curating recommendations from the user's weekend cultural watchlist. |
| triage_inbox_prompt | Prompt for triaging unarmed thoughts, tasks, and overdue reminders. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| reminders_resource | Resource returning active reminders as JSON. |
| watchlist_resource | Resource returning queued watchlist and cultural items as JSON. |
| stats_resource | Resource returning system and ledger statistics as JSON. |
| now_playing_resource | Resource returning current background media playback state as JSON. |
TDQS
Scored across 17 tools
Tools are mostly cleanly separated by domain: reminders, tasks, phone notifications, cultural items, and music. There is some conceptual overlap between reminders and tasks, and between resolve_music_query and play_music, but descriptions make the intended boundaries workable.
Most action tools follow a snake_case verb_noun pattern (create_reminder, list_open_tasks, complete_task, play_music). A few read tools use noun-first labels such as task_stats, latest_otp, last_whatsapp, and missed_summary, and create/capture are used inconsistently for similar creation actions, but naming remains readable.
At 17 tools the surface is slightly above the ideal 3-15 range, but it covers five distinct subdomains: tasks, reminders, notifications, cultural items, and music. Each tool appears to earn its place rather than being redundant bulk.
Core flows for tasks and reminders are present: create, list, complete, and for tasks also search/drop/stats. However, there are notable lifecycle gaps: reminders and tasks lack explicit update/edit and delete operations, cultural items can be captured/listed but not marked consumed, and music playback has no stop/control counterpart.