Stickies
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stickies_writeA | Create a persistent sticky note. Call this when a durable fact emerges (a decision, blocker, preference, context, or todo) that future sessions should retain. |
| stickies_readA | Retrieve active stickies relevant to the current session, ordered by importance. |
| stickies_dismissA | Soft-delete a sticky by id (marks it dismissed; it is no longer read back). |
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 3 tools
Each tool performs a distinct operation: reading, softening deletion, and creating stickies. No overlap or ambiguity between them.
All tools follow a consistent 'stickies_verb' pattern with clear action verbs (read, dismiss, write).
Three tools is well-scoped for a simple sticky-note system, covering the essential operations without bloat.
The tool surface covers the full lifecycle of a sticky: create, read, and dismiss. No obvious missing operations for the domain.