chamber
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAMBER_PYTHON | No | Path to a Python interpreter with onnxruntime, used for the embedder. | |
| CHAMBER_API_KEY | No | API key for external OpenAI-compatible endpoints when model.base is not a loopback address. |
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 |
|---|---|
| chamber_askA | Ask a question of the local Chamber corpus and get an answer whose every claim is judged against its own citations. Each claim comes back ALLOWED (its cited passages verified against their stored hashes) or UNSUPPORTED (no verified source — recorded, not load-bearing). Cited sources are returned as file#passage references you can open. Answers only from the indexed corpus; says so when nothing matches. NOTE: this WRITES, exactly as |
| chamber_verifyA | Re-check every stored belief's pinned sources against the corpus as it stands now, and report the ones whose evidence moved: a source that no longer exists (not_found) or whose text changed under the pin (hash_mismatch). This is drift detection — the conclusion did not change, the ground under it did. Read-only. |
| chamber_corpusA | Report what is actually in the index: passage and file counts, source kinds and which of them are citable, the top contributing folders, and any file far above the median passage count (the signature of an export rather than a note). Use this before trusting a 'nothing matches' answer. Read-only. |
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 3 tools
Each tool has a clearly distinct purpose: ask queries and records answers, verify checks for drift in stored beliefs, and corpus inspects the index. There is no overlap in their functionality.
All tools follow a consistent pattern of 'chamber_' followed by a single lowercase word (ask, verify, corpus). Though one is a noun, the convention is uniform and predictable.
Three tools is within the ideal range and each serves a necessary, non-redundant role for the server's purpose of querying and maintaining a citation-verified corpus.
The set covers the full workflow: query with verification (ask), maintain confidence (verify), and understand the index (corpus). No obvious missing operations for the stated domain.