Recall by Polign
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PGPASSWORD | No | PostgreSQL password when using the pgvector backend if it is not included in DATABASE_URL. | |
| POLIGN_URL | No | URL of the polign-server to use for shared memory. | |
| QDRANT_URL | No | Qdrant server URL when using the Qdrant backend. | |
| RECALL_URL | No | URL of a recall serve instance for recall connect. | |
| MONGODB_URI | No | MongoDB connection URI when using the MongoDB backend, e.g. mongodb://user:password@localhost:27017/recall. | |
| DATABASE_URL | No | PostgreSQL connection URL when using the pgvector backend, e.g. postgres://user:password@localhost:5432/mydb. | |
| POLIGN_API_KEY | No | API key for polign_db when authentication is required. | |
| QDRANT_API_KEY | No | Qdrant API key when using the Qdrant backend. | |
| RECALL_API_KEY | No | API key for a recall serve instance for recall connect. | |
| MONGODB_PASSWORD | No | MongoDB password when using the MongoDB backend if it is not included in MONGODB_URI. | |
| POLIGN_COLLECTION | No | Collection name used for shared memory on polign-server. | |
| RECALL_TOKEN_FILE | No | Path to a projected service account token file for Kubernetes-based recall connect authentication. |
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 |
|---|---|
| rememberA | Keep something worth remembering about the user or their work: a preference, a fact, a decision, or a correction. Pass the passage as text, in the user's words where you can, or pass the conversation as messages with their roles, so that only what the user said or agreed to is kept and nothing the assistant suggested. The server works out what it says. A newer statement replaces an older one about the same thing, and the older one stays in the history. Restating something already known changes nothing. |
| recallA | Ask what is remembered, in words, before assuming anything about the user. Answers are what is believed now, as sentences. Each lists under before what it replaced and when, so a correction comes with the answer, and under elsewhere anything else believed about the same thing in other words, such as a later dislike beside a like; the newer statement usually holds. days_ago says how long ago it was stated. A time named in the question, such as "last week", is searched first. Each also gives under said the sentence it was drawn from, as the user said it. Pass as_of to ask what was believed at an earlier instant. Leave out question to get everything believed about the user, a profile to start a conversation with. Pass since to get only what changed after then, newest first: at the start of a session, since the last one, it says what is new. |
| forgetA | Stop believing what a description names, such as "my editor" or "that I live in Lisbon". Returns what was withdrawn. Nothing is deleted: it stays in the history, and remembering it again brings it back. |
| historyA | How something remembered changed, in words: every statement about it, oldest first, each with what it began and ended believing, and what is believed now. Use it when the user asks what changed, when, or why something is believed, and to show a correction whole. Something since forgotten still has its history. |
| diffA | What was believed differently at one instant than at another: each thing that began or stopped being believed in between. Use it to say what changed over a period, such as since the last session or during an incident. |
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
The five tools cover clearly different operations: storing, querying, withdrawing, tracing one item's history, and comparing beliefs across time. The only mild overlap is between recall's `since` mode and diff, which both answer 'what changed', though their descriptions differentiate instants versus periods.
All names are single, lowercase words with a consistent terse style. However, remember/recall/forget are verbs while history and diff are nouns, a minor deviation from a pure verb convention.
Five tools is well scoped for a focused memory service, with each tool earning its place across the read/write/history lifecycle. No tool feels redundant or missing from the core set.
The surface covers the full memory lifecycle: write (remember), read (recall with profile, point-in-time, and delta views), soft delete (forget), per-item history, and cross-instant diff. No dead ends are apparent for the stated purpose.