Chronicle
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PCG_LM_MODEL | Yes | Model identifier for Qwen (default qwen/qwen3-14b) | |
| PCG_LM_API_KEY | Yes | API key for LM Studio (placeholder accepted if authentication disabled) | |
| PCG_LM_BASE_URL | Yes | Base URL for the LM Studio local server (default http://127.0.0.1:1234/v1) | |
| PCG_TRIAGE_MAX_CHARS | Yes | Maximum characters for triage (default 24000) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | List enabled sources and whether each is ready. |
| searchB | Search selected sources. Returns bounded snippets with provenance and stable IDs. |
| search_insightsA | Search locally generated keep-only summaries. Use record_id with fetch to inspect evidence. |
| get_document_memoryB | Get a compact overview. Sections are excluded by default and always strictly capped. |
| search_document_memoryB | Search detailed page-cited memories. Returns at most 10 bounded section summaries. |
| fetch_document_sectionA | Fetch one exact detailed memory section returned by search_document_memory. |
| fetchA | Fetch one exact item returned by search. Never accepts raw paths or URLs. |
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 7 tools
The tools target distinct resources (sources, insights, document memory, sections) with clear action verbs. Search and search_document_memory could be confused, but descriptions specify different targets, making the separation mostly clear.
All tool names use snake_case and follow a mostly predictable verb_noun pattern (list_sources, search_insights). A few names like 'search' and 'fetch' lack an explicit object, which creates minor inconsistency, but the style is uniform.
With 7 tools, the count is well within the ideal range and each tool seems purposefully designed to cover a distinct operation in the search/retrieval workflow, earning its place.
The set covers listing sources, searching multiple data types, and fetching specific items or sections, which is complete for a read-only retrieval system. A minor gap is the lack of a way to browse all memory sections without searching, but it's not a major dead end.