Phygital Engram
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGRAM_DATA | Yes | Path to a separate folder where Phygital Engram keeps its own index and files. It must be outside your notes folder. | |
| ENGRAM_VAULT | Yes | Path to your folder of Markdown notes (the vault) to search. It must contain a file named CLAUDE.md at the top, which can be empty. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search the person's Markdown notes with plain words and get a short ranked list. Use it first, before you answer about their past work, projects, decisions, people or notes. Read-only. Each result has an id, the note path, the heading, the date, a snippet and a line saying why it came back (for example an exact match or a decision note). Results can include a private note marked LOCKED: tell the person it exists and let them open it. Pass an id to open_result for the full text. If nothing matches, the list is empty. |
| open_resultA | Open one result from search_notes by its id and return the full section of the note, or the whole note if it is short. Read-only. Use it after search_notes, when a snippet is not enough to answer. An id that no longer exists returns a not-found message: search again. A LOCKED private note is refused, and the person must open it themselves. |
| around_resultA | Show the sections just before and after one result from search_notes, plus other notes written the same day. Read-only. Use it when a result looks right but you need the context around it, such as the step before a decision or the rest of a day. It does not search: it needs a result id. |
| check_indexA | Report whether the search index is fresh, whether anything private slipped in, and whether searches are fast. Read-only: it changes nothing and needs no input. Use it when results look old or missing, or when the person asks if search is healthy. |
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 4 tools
The four tools split cleanly by input contract: search_notes takes a query, open_result and around_result take a result id, and check_index takes nothing. The only soft overlap is between open_result and around_result, since both return note text for an id, but the descriptions explicitly separate 'full section' from 'surrounding context' and even state that around_result does not search.
All four names are snake_case verb_noun pairs (search_notes, open_result, around_result, check_index), matching the expected pattern. The minor deviation is 'around_result', which uses a preposition rather than an action verb and shifts the object noun from 'notes' to 'result'.
Four tools cover a tight read-only retrieval loop — discover, open, expand context, verify health — and each earns its place with no redundant surface. It sits at the low end, but nothing feels gratuitous; the only pressure toward a fifth tool is a browse/list path that doesn't exist.
The stated purpose (search a person's notes and open what you find) is fully covered, including context expansion and a self-diagnostic for stale or private content. The gap is enumeration: there is no way to list recent notes, browse by date, or enumerate people/tags, so questions like 'what did I work on last week' depend entirely on guessing search terms, only partly mitigated by around_result returning same-day notes.