Skip to main content
Glama

step_by_step_analysis

Perform detailed step-by-step analysis of complex tasks by breaking them down into manageable components for systematic problem-solving.

Instructions

step by step|one at a time|gradually|step by step|one by one|gradually - Perform detailed step-by-step analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesTask to analyze step by step
contextNoAdditional context for the task
detailLevelNoLevel of detail

Implementation Reference

  • The main execution function for the 'step_by_step_analysis' tool. It generates a detailed step-by-step breakdown with actions, checkpoints, time estimates, and summary based on the input task, optional context, and detail level.
    export async function stepByStepAnalysis(args: { task: string; context?: string; detailLevel?: string }): Promise<ToolResult> {
      const { task, context = '', detailLevel = 'detailed' } = args;
      
      const stepCount = detailLevel === 'basic' ? 3 : detailLevel === 'detailed' ? 5 : 7;
      const stepAnalysis = {
        action: 'step_by_step_analysis',
        task,
        context,
        detailLevel,
        steps: Array.from({ length: stepCount }, (_, i) => {
          const stepNum = i + 1;
          return {
            stepNumber: stepNum,
            title: `Step ${stepNum}: ${task} - Phase ${stepNum}`,
            description: `Detailed analysis of ${task} in step ${stepNum}`,
            actions: [
              `Analyze requirements for step ${stepNum}`,
              `Identify dependencies and prerequisites`,
              `Execute the planned actions`,
              `Validate results and check for issues`,
              `Prepare for next step`
            ],
            checkpoints: [
              `Verify step ${stepNum} requirements are met`,
              `Confirm outputs are as expected`,
              `Check for any blocking issues`
            ],
            estimatedTime: detailLevel === 'comprehensive' ? `${stepNum * 10} minutes` : `${stepNum * 5} minutes`
          };
        }),
        summary: {
          totalSteps: stepCount,
          estimatedTotalTime: detailLevel === 'comprehensive' ? `${stepCount * 35} minutes` : `${stepCount * 20} minutes`,
          complexity: detailLevel === 'basic' ? 'low' : detailLevel === 'detailed' ? 'medium' : 'high'
        },
        status: 'success'
      };
      
      return {
        content: [{ type: 'text', text: `Task: ${task}\nDetail: ${detailLevel}\nSteps: ${stepCount}\n\n${stepAnalysis.steps.map(s => `Step ${s.stepNumber}: ${s.title}\n  Time: ${s.estimatedTime}\n  Actions: ${s.actions.join(', ')}\n  Checkpoints: ${s.checkpoints.join(', ')}`).join('\n\n')}\n\nTotal Time: ${stepAnalysis.summary.estimatedTotalTime} | Complexity: ${stepAnalysis.summary.complexity}` }]
      };
    }
  • The ToolDefinition export that specifies the tool's name, description, input schema (with task required, optional context and detailLevel), and annotations for the MCP protocol.
    export const stepByStepAnalysisDefinition: ToolDefinition = {
      name: 'step_by_step_analysis',
      description: 'step by step|one at a time|gradually|step by step|one by one|gradually - Perform detailed step-by-step analysis',
      inputSchema: {
        type: 'object',
        properties: {
          task: { type: 'string', description: 'Task to analyze step by step' },
          context: { type: 'string', description: 'Additional context for the task' },
          detailLevel: { type: 'string', description: 'Level of detail', enum: ['basic', 'detailed', 'comprehensive'] }
        },
        required: ['task']
      },
      annotations: {
        title: 'Step-by-Step Analysis',
        audience: ['user', 'assistant']
      }
    };
  • src/index.ts:620-621 (registration)
    Registration in the executeToolCall switch statement that maps the tool name to its handler function for execution.
    case 'step_by_step_analysis':
      return await stepByStepAnalysis(args as any) as CallToolResult;
  • src/index.ts:115-115 (registration)
    Inclusion of the tool definition in the global 'tools' array, enabling it for MCP ListTools requests and discovery.
    stepByStepAnalysisDefinition,
  • src/index.ts:83-83 (registration)
    Import statement that brings the handler and definition into the main index file for registration.
    import { stepByStepAnalysis, stepByStepAnalysisDefinition } from './tools/thinking/stepByStepAnalysis.js';
Behavior2/5

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

Annotations only provide a title ('Step-by-Step Analysis'), so the description carries the full burden of behavioral disclosure. It mentions 'detailed' and 'step-by-step' but does not explain what the tool actually does behaviorally—e.g., whether it generates a list, provides explanations, iterates through sub-tasks, or has side effects. No information on permissions, rate limits, or output format is given.

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

Conciseness2/5

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

The description is inefficiently structured with repetitive phrases ('step by step|one at a time|gradually|step by step|one by one|gradually') that waste space without adding value. It is not front-loaded with clear purpose, and the redundancy reduces clarity rather than enhancing it.

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 no annotations beyond title, no output schema, and a general-purpose tool with 3 parameters, the description is incomplete. It fails to explain what the tool outputs, how it behaves, or its role among many analysis-focused siblings. For a tool that likely produces structured analysis, more context is needed to guide 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 (task, context, detailLevel) with descriptions and enum values. The description adds no meaning beyond this, not even hinting at how parameters affect the analysis. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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

Purpose2/5

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

The description 'Perform detailed step-by-step analysis' is a tautology that essentially restates the tool name 'step_by_step_analysis' with minimal elaboration. While it includes the verb 'perform' and resource 'analysis', it lacks specificity about what kind of analysis or what distinguishes it from sibling tools like 'break_down_problem' or 'think_aloud_process'.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools focused on analysis (e.g., 'analyze_complexity', 'analyze_problem', 'break_down_problem'), there is no indication of context, prerequisites, or exclusions. The repetitive phrasing 'step by step|one at a time|gradually' hints at a methodical approach but fails to specify use cases.

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/ssdeanx/ssd-ai'

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