Backstory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKSTORY_DB | No | Path to the SQLite database file. Defaults to ~/.backstory/backstory.db |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_entityC | Look up a person or place by name and return the matching entity. |
| search_timelineB | Search the user's life timeline with a natural-language query. Returns ranked events with timestamp, source and text. |
| list_sourcesA | List the sources ingested into this vault and how many events each contributed. |
| get_eventsA | Fetch full event records by id, including the pointer to the original source record. |
| summarize_periodC | Return all events in a time range so the agent can summarize what happened. |
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 has a clearly distinct purpose: event retrieval by ID, source listing, entity lookup, semantic timeline search, and time-range summarization. No overlap.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_events, list_sources), making naming predictable and clear.
Five tools is appropriate for a focused query/summary server, covering core operations without being overwhelming or insufficient.
Covers key query scenarios (by ID, search, time range, source list) but lacks event mutations (create/update/delete), which fits the likely read-only domain. Minor gap: no direct way to get events by source.