sortwell
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SORTWELL_DIR | No | Directory where the JSONL data files are stored. Defaults to ~/.sortwell. | |
| TYPESAFE_API_KEY | Yes | Your TypeSafe API key. Required for the server to function. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| captureA | Save something the user wants kept: a note, a link, an email, a line from a meeting, anything. Call it once per distinct item; paste a transcript one item at a time rather than all at once. It decides for itself what kind of thing the item is, which of the user's projects it belongs to, whether it needs attention, and whether they already have it, then files it. The text is stored exactly as given and never rewritten. You do not need to classify anything yourself, and you should not ask the user which project it belongs to. |
| shortlistA | The few things that matter today, ranked out of everything still open, with any projects that have gone quiet. Call it when the user asks what they should be doing, what is outstanding, or at the start of a working session. Takes no arguments. |
| add_projectA | Add a project or an area so captured items have somewhere to go. A project finishes; an area is ongoing. The scope line is what routing is judged against, so write it as a plain description of what belongs here rather than a title. |
| mark_doneA | Mark an item finished so it leaves the shortlist. Nothing is deleted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: capture saves items, shortlist shows priorities, add_project creates routing targets, and mark_done changes item state. No two tools could plausibly be confused for the same operation.
All tool names are lowercase imperative verbs, with compound names using underscores (add_project, mark_done). The naming pattern is uniform and predictable across the set.
Four tools cover the full capture-to-completion loop without redundancy. The count is well-matched to the server's focused personal-information-management purpose.
The core workflow (capture, route, shortlist, mark done) is fully covered. A minor gap is the lack of a way to browse or search all captured items that fall off the shortlist, but this is workable for the stated use case.