Atom of Thoughts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| viz | No | Visualization mode: auto, always, or never | auto |
| mode | No | Which tools to register: full, fast, or both | both |
| max-depth | No | Override depth limit | 5 |
| output-dir | No | Where to write viz HTML | OS temp |
| downloads-dir | No | Approval JSON fallback | ~/Downloads |
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 |
|---|---|
| AoT-fastA | Default structured reasoning. Decomposes problems into atomic thoughts with dependency tracking. Depth 3. Use for: think-through, analyze, reason about tradeoffs, debug root causes, evaluate alternatives, make decisions. Most reasoning tasks belong here. Trigger phrases: "think through", "analyze", "reason about", "debug", "evaluate options", "compare approaches". Atom types: premise (facts) → reasoning (logic) → hypothesis (proposals) → verification (checks) → conclusion (answer). Minimal 3-call example: Call 1: {atomId:"P1", content:"The API returns 500 on POST /users", atomType:"premise"} Call 2: {atomId:"R1", content:"500 suggests unhandled exception in route handler", atomType:"reasoning", dependencies:["P1"]} Call 3: {atomId:"C1", content:"Add try-catch in POST /users handler", atomType:"conclusion", dependencies:["R1"], confidence:0.9} Only atomId, content, and atomType are required. dependencies defaults to [], confidence defaults to 0.7. Use AoT-full instead when you need >5 reasoning steps, multi-angle verification, or decomposition of sub-problems. viz param: only set viz:true when the user explicitly asks to see the graph or says "visualize". Never set it automatically. |
| AoT-fullA | Deep structured reasoning with decomposition-contraction. Depth 5. Use for: implementation plans, architecture decisions, multi-step verification, problems that decompose into sub-problems. Trigger phrases: "plan", "design", "megathink", "full AoT", /aot-plan. Same atom types and parameters as AoT-fast. Drives decomposition via the atomcommands tool (decompose → sub-atoms → complete_decomposition). Reach for AoT-fast first unless you genuinely need the extra depth or decomposition. viz param: only set viz:true when the user explicitly asks to see the graph or says "visualize". Never set it automatically. |
| atomcommandsB | Lifecycle and meta operations for the current AoT session. Commands:
|
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: AoT-fast handles simple structured reasoning, AoT-full handles deep reasoning with decomposition, and atomcommands manages lifecycle operations. There is no ambiguity about which tool to use for a given task.
Naming is somewhat inconsistent: two tools use the prefix 'AoT-' (AoT-fast, AoT-full) while the third uses a different style (atomcommands). This mixed convention makes the set less predictable but still readable.
Three tools is on the low side for a reasoning server that offers multiple capabilities (simple reasoning, deep reasoning, lifecycle operations). The boundary between AoT-fast and AoT-full could be merged into one tool with a depth parameter, and atomcommands bundles many features into one tool.
The tool set covers the core reasoning workflow (simple and deep) and all necessary life-cycle operations (sessions, decomposition, export). Minor gaps exist, such as a dedicated tool to list atoms in a session, but these can be addressed via existing commands like export.