ThoughtDAG
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| why_checkA | Cheap first question before editing a file: does this artifact have any history in local agent sessions? One line; history true/false. |
| why_fileC | The turns across local Claude Code, Codex, DeepSeek Harness, Pi and ThoughtDAG sessions that touched a file, URL or paper: when, what changed (Δ, observed), what was asked, what the answer said about it (≈, a candidate explanation, not a verified reason). Each hit carries a deep link. |
| findC | Where these exact words were asked (Q), answered (A) or attached (M) across local sessions, canvases and the memories Claude Code and Codex keep for themselves. Exact, case-insensitive match; every hit is a verbatim snippet with a pointer. |
| recall_turnA | One turn in full — the question, the answer, the tool calls with their diffs — by session id (or prefix) and turn number as shown by why_file. |
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 separate along clear axes: find does keyword search, why_file retrieves turns touching a specific artifact, why_check gives a quick boolean for artifacts, and recall_turn fetches a specific turn. why_check is a lightweight version of why_file and find overlaps with why_file for file-related queries, but the descriptions make intended usage clear.
All names use lowercase snake_case, but the patterns are mixed: find is a bare verb, recall_turn is verb_noun, while why_check and why_file use a why_ prefix. The inconsistency is readable but not a uniform verb_noun convention.
With only four tools, the set is tightly scoped for a session-history retrieval server, and each tool serves a distinct retrieval depth (keyword search, artifact existence check, artifact history, full turn). No obvious filler tools are present.
The surface covers keyword search, artifact-based history, existence checks, and full-turn retrieval, which supports the core recall workflows. It lacks session enumeration or time-range filtering, but agents can work around these gaps by searching known terms.