Skip to main content
Glama
dioptx
by dioptx

atomcommands

Manage reasoning session lifecycle: break atoms into sub-atoms, check termination status, export atom graph, and switch between sessions for structured decomposition.

Instructions

Lifecycle and meta operations for the current AoT session.

Commands:

  • decompose: Break an atom into sub-atoms (requires atomId)

  • complete_decomposition: Finish a decomposition (requires decompositionId)

  • termination_status: Check if reasoning should stop

  • best_conclusion: Get the highest-confidence verified conclusion

  • set_max_depth: Change max depth limit (requires maxDepth)

  • export: Export the current atom graph as JSON for analysis or visualization (optional title)

  • check_approval: Poll for browser-based approval decisions (optional downloadsDir, sessionStartTime)

  • new_session: Create and switch to a new session (optional sessionId; auto-generated if omitted)

  • switch_session: Activate an existing session (requires sessionId)

  • list_sessions: List all sessions with status and atom counts

  • reset_session: Wipe atoms in a session (defaults to active)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to execute
atomIdNoAtom ID (for decompose)
decompositionIdNoDecomposition ID (for complete_decomposition)
maxDepthNoMaximum depth (for set_max_depth)
titleNoOptional title (for export)
downloadsDirNoOverride downloads directory (for check_approval)
sessionStartTimeNoUnix timestamp to ignore older approval files (for check_approval)
sessionIdNoSession ID (for new_session/switch_session/reset_session, optional for new_session/reset_session)
Behavior3/5

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

Since annotations are absent, the description carries full burden. It discloses some behavioral traits (e.g., 'Wipe atoms' for reset_session, 'requires atomId' for decompose), but lacks details on error conditions, ordering constraints, or state changes. No contradictions with annotations.

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?

The description is well-structured with a list of commands and their details. It is fairly concise given the number of subcommands, though some verbosity could be trimmed (e.g., repeating 'requires' in each item).

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

Completeness2/5

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

No output schema exists, yet the description fails to explain what each command returns (e.g., does export return JSON? does list_sessions return a list?). It also omits prerequisites like needing an active session. These gaps hinder an AI agent from fully understanding the tool's behavior.

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

Parameters3/5

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

The input schema already provides descriptions for all parameters (schema_coverage=100%). The description adds minimal value beyond repeating which command uses which parameter, so it does not significantly enhance meaning.

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

Purpose4/5

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

The description clearly states that the tool handles 'lifecycle and meta operations for the current AoT session' and enumerates multiple subcommands with brief explanations. However, it does not differentiate from sibling tools (AoT-fast, AoT-full) which likely have overlapping functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus its siblings (AoT-fast, AoT-full). The description only lists available commands without context on selecting this tool over others.

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