StickyInc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | API key for OpenAI (direct provider) | |
| STICKYINC_MODEL | No | Override the model for any provider | |
| ANTHROPIC_API_KEY | No | API key for Anthropic (direct provider) | |
| OPENROUTER_API_KEY | No | API key for OpenRouter |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskA | Add a todo to StickyInc. The user sees it appear in their floating pane. |
| add_task_naturalA | Parse a free-text phrase like 'call dentist Friday 3pm' into a task with optional due date, using the configured LLM (Anthropic/OpenRouter/OpenAI). |
| list_tasksB | List open StickyInc tasks (or all, with include_completed=true). |
| complete_taskA | Mark a StickyInc task done by id. |
| list_doneA | List recently completed StickyInc tasks, with optional archive of older completions. |
| schedule_eventB | Schedule an event. v0.1 stores as a dated task; v0.3 will call Google Calendar create_event. |
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
Most tools have clearly distinct purposes: add_task vs add_task_natural differ in input method, list_done vs list_tasks separate completed from open items, and schedule_event is unique. Slight overlap between add_task and add_task_natural but descriptions clarify.
Tools mostly follow a verb_noun pattern (add_task, complete_task, list_done, list_tasks, schedule_event). The exception is add_task_natural, which adds a qualifier but still consistent in style. No mixing of conventions.
With 6 tools, the server is well-scoped for a focused task management assistant. Each tool addresses a core operation without unnecessary bloat or excessive specialization.
Basic create (add tasks), read (list tasks/done), and update (mark done) are covered, but missing update/edit task, delete task, and event scheduling is still immature (v0.1). Gaps may cause agent failures for common workflows.