references
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REFERENCES_DIR | No | Your library, taste log and live cache | ~/.references |
| REFERENCES_LIVE | No | `0` turns off live pulls (canon + library only) | 1 |
| REFERENCES_LIBRARIES | No | Extra read-only folders of references (`:`-separated) | none |
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 |
|---|---|
| references_suggestA | Curated references, brought to the user. Call this BEFORE you design or generate anything with a look or a voice (UI, landing page, app screen, deck, video, motion, animation, social post, written post, ad creative) so the work starts from proven work instead of an AI default. Returns ranked |
| references_shortlistA | Show the person the references YOU chose for this project: pass the ids you picked from a references_suggest pool (call it with |
| references_getB | Full detail of one reference by id (from references_suggest). |
| references_pickB | Record which reference the user chose (and any note like "more like this but warmer"). Saves to their taste log so future suggestions lean their way; returns the take/url/image to build against. |
| references_addA | Save a reference the user handed you (a link, a screenshot path, or both) into their library so it is suggested from now on. Always capture |
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 5 tools
Each tool occupies a distinct stage in the reference workflow: suggest discovers a pool, shortlist presents chosen candidates, get retrieves details by id, pick records the user's choice, and add saves a new reference. The descriptions make the boundaries clear, especially the pool-to-shortlist-to-pick sequence.
All tools use a consistent `references_` prefix followed by a concise verb: suggest, shortlist, get, pick, add. The pattern is predictable and readable throughout.
Five tools are well-scoped for a reference discovery and taste-capture workflow. Each tool has a clear role and none feels redundant or excessive.
The surface covers the core lifecycle: discovery, shortlisting, detail retrieval, selection feedback, and saving new references. It lacks explicit update/delete operations for the user's saved library, but those are minor gaps for the stated purpose.