Skip to main content
Glama

atomcommands

Control decomposition, check termination status, retrieve conclusions, and adjust depth settings for the Atom-of-Thoughts reasoning process.

Instructions

A command tool to control the decomposition-contraction mechanism and automatic termination of Atom of Thoughts.

Use this tool to access advanced features of AoT:

  1. Decomposition (decompose): Decompose a specified atom into smaller sub-atoms

  2. Complete decomposition (complete_decomposition): Complete an ongoing decomposition process

  3. Check termination status (termination_status): Check the termination status of the current AoT process

  4. Get best conclusion (best_conclusion): Get the verified conclusion with the highest confidence

  5. Change settings (set_max_depth): Change the maximum depth limit

Command descriptions:

  • command: Command to execute (decompose, complete_decomposition, termination_status, best_conclusion, set_max_depth)

  • atomId: Atom ID to use with the command (only required for decompose command)

  • decompositionId: ID of the decomposition process (only required for complete_decomposition command)

  • maxDepth: Maximum depth value to set (only required for set_max_depth command)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to execute
atomIdNoAtom ID to use with the command
decompositionIdNoID of the decomposition process to complete
maxDepthNoMaximum depth value to set

Implementation Reference

  • Main handler logic for the 'atomcommands' tool. Dispatches to AtomOfThoughtsServer methods based on the 'command' parameter (decompose, complete_decomposition, termination_status, best_conclusion, set_max_depth).
    } else if (request.params.name === "atomcommands") {
      try {
        const params = request.params.arguments as Record<string, unknown>;
        const command = params.command as string;
        
        let result: any = { status: 'error', message: 'Unknown command' };
        
        switch (command) {
          case 'decompose':
            const atomId = params.atomId as string;
            if (!atomId) throw new Error('atomId is required for decompose command');
            
            const decompositionId = atomServer.startDecomposition(atomId);
            result = { 
              status: 'success', 
              command: 'decompose',
              decompositionId,
              message: `Started decomposition of atom ${atomId}`
            };
            break;
            
          case 'complete_decomposition':
            const decompId = params.decompositionId as string;
            if (!decompId) throw new Error('decompositionId is required for complete_decomposition command');
            
            const completed = atomServer.completeDecomposition(decompId);
            result = { 
              status: 'success', 
              command: 'complete_decomposition',
              completed,
              message: `Completed decomposition ${decompId}`
            };
            break;
            
          case 'termination_status':
            const status = atomServer.getTerminationStatus();
            result = { 
              status: 'success', 
              command: 'termination_status',
              ...status
            };
            break;
            
          case 'best_conclusion':
            const bestConclusion = atomServer.getBestConclusion();
            result = { 
              status: 'success', 
              command: 'best_conclusion',
              conclusion: bestConclusion ? {
                atomId: bestConclusion.atomId,
                content: bestConclusion.content,
                confidence: bestConclusion.confidence
              } : null
            };
            break;
            
          case 'set_max_depth':
            const maxDepth = params.maxDepth as number;
            if (typeof maxDepth !== 'number' || maxDepth <= 0) 
              throw new Error('maxDepth must be a positive number');
            
            atomServer.maxDepth = maxDepth;
            result = { 
              status: 'success', 
              command: 'set_max_depth',
              maxDepth,
              message: `Maximum depth set to ${maxDepth}`
            };
            break;
        }
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              status: 'error',
              error: error instanceof Error ? error.message : String(error)
            }, null, 2)
          }],
          isError: true
        };
      }
    }
  • Tool definition and input schema for 'atomcommands', specifying available commands and parameters.
    const ATOM_COMMANDS_TOOL: Tool = {
      name: "atomcommands",
      description: `A command tool to control the decomposition-contraction mechanism and automatic termination of Atom of Thoughts.
      
    Use this tool to access advanced features of AoT:
    
    1. Decomposition (decompose): Decompose a specified atom into smaller sub-atoms
    2. Complete decomposition (complete_decomposition): Complete an ongoing decomposition process
    3. Check termination status (termination_status): Check the termination status of the current AoT process
    4. Get best conclusion (best_conclusion): Get the verified conclusion with the highest confidence
    5. Change settings (set_max_depth): Change the maximum depth limit
    
    Command descriptions:
    - command: Command to execute (decompose, complete_decomposition, termination_status, best_conclusion, set_max_depth)
    - atomId: Atom ID to use with the command (only required for decompose command)
    - decompositionId: ID of the decomposition process (only required for complete_decomposition command)
    - maxDepth: Maximum depth value to set (only required for set_max_depth command)`,
      inputSchema: {
        type: "object",
        properties: {
          command: {
            type: "string",
            enum: ["decompose", "complete_decomposition", "termination_status", "best_conclusion", "set_max_depth"],
            description: "Command to execute"
          },
          atomId: {
            type: "string",
            description: "Atom ID to use with the command"
          },
          decompositionId: {
            type: "string",
            description: "ID of the decomposition process to complete"
          },
          maxDepth: {
            type: "number",
            description: "Maximum depth value to set"
          }
        },
        required: ["command"]
      }
    };
  • src/index.ts:771-773 (registration)
    Registration of the 'atomcommands' tool (as ATOM_COMMANDS_TOOL) in the server's listTools response.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [AOT_TOOL, AOT_LIGHT_TOOL, ATOM_COMMANDS_TOOL],
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It mentions 'automatic termination' and 'decomposition-contraction mechanism' but doesn't explain what these entail, such as side effects, permissions needed, or response formats. For a multi-command tool with mutation operations (e.g., decompose, set_max_depth), this is a significant gap in safety and operational context.

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 clear purpose statement, numbered command list, and parameter notes. It's front-loaded with the main purpose, but could be more concise by integrating parameter details more tightly. Every sentence adds value, though some redundancy exists between the command list and parameter descriptions.

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?

Given the complexity of a multi-command tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context for mutations, doesn't explain return values or error handling, and omits prerequisites like authentication. For a tool with advanced features and potential side effects, more guidance is needed to ensure safe and effective use.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by specifying which parameters are required for each command (e.g., 'only required for decompose command'), but doesn't provide additional meaning beyond what the schema offers, such as format examples or constraints. Baseline 3 is appropriate given high schema coverage.

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 this is a 'command tool to control the decomposition-contraction mechanism and automatic termination of Atom of Thoughts,' providing specific verbs (decompose, check, get, change) and resources (atoms, decomposition processes, conclusions, settings). It distinguishes from sibling tools by mentioning 'advanced features of AoT' but doesn't explicitly contrast with AoT or AoT-light beyond this implication.

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

Usage Guidelines3/5

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

The description says 'Use this tool to access advanced features of AoT,' which implies when to use it (for advanced control) but doesn't specify when NOT to use it or explicitly name alternatives like AoT or AoT-light. It lists five commands but doesn't guide on choosing between them or contextual prerequisites.

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/kbsooo/MCP_Atom_of_Thoughts'

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