Skip to main content
Glama
dioptx
by dioptx

AoT-fast

Break down complex problems into atomic thoughts with dependency tracking to reason through tradeoffs, debug root causes, evaluate alternatives, and make decisions.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atomIdYesUnique identifier for the atom (e.g., 'P1', 'R1', 'H1', 'C1')
contentYesThe thought content of this atom
atomTypeYesType of atom
dependenciesNoIDs of atoms this depends on (default: [])
confidenceNoConfidence 0-1 (default: 0.7)
isVerifiedNoWhether this atom has been verified
depthNoDepth level (auto-calculated if omitted)
vizNoRender and open a D3 visualization of the current graph after this atom (default: false). Set true during planning or when the user is reviewing your reasoning; leave false during execution.
sessionIdNoTarget session for this atom (default: active session). Sessions isolate atom graphs so two reasoning problems in one process don't collide. Use atomcommands new_session/switch_session to manage explicitly. Auto-spawned on next zero-dep atom after a session terminates.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but description covers depth, atom types, required/optional fields, defaults, and viz param usage. Could add read-only hint but not critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections, bullet points, and example, though slightly long. Front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, no output schema, description covers usage, parameters, and behavior comprehensively. Example helps. Lacks return value info but acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet description adds significant value: explains defaults, provides example, clarifies viz and sessionId usage, and gives atom type enum semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it's for structured reasoning, lists specific use cases and trigger phrases, and distinguishes from sibling tool AoT-full.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (think-through, analyze, etc.) and when not (use AoT-full for complex cases), including trigger phrases and alternative tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dioptx/mcp-atom-of-thoughts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server