Skip to main content
Glama

bmad_parse_specification

Parse business specification documents to extract requirements and generate actionable tasks for project implementation.

Instructions

Parse a business specification document and generate tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe specification content to parse
formatYesFormat of the specification content
generateTasksNoWhether to automatically generate tasks from requirements
autoAssignNoWhether to automatically assign tasks to agents
validateNoWhether to validate generated tasks

Implementation Reference

  • The MCP tool handler for 'bmad_parse_specification' that delegates execution to BMADService.parseSpecification with the provided arguments.
    tools.set('bmad_parse_specification', async (args: any) => {
      return await bmadService.parseSpecification(args);
    });
  • Input schema and metadata definition for the bmad_parse_specification tool.
    {
      name: 'bmad_parse_specification',
      description: 'Parse a business specification document and generate tasks',
      inputSchema: {
        type: 'object',
        properties: {
          content: {
            type: 'string',
            description: 'The specification content to parse'
          },
          format: {
            type: 'string',
            enum: ['markdown', 'yaml', 'plain'],
            description: 'Format of the specification content'
          },
          generateTasks: {
            type: 'boolean',
            description: 'Whether to automatically generate tasks from requirements',
            default: true
          },
          autoAssign: {
            type: 'boolean',
            description: 'Whether to automatically assign tasks to agents',
            default: false
          },
          validate: {
            type: 'boolean',
            description: 'Whether to validate generated tasks',
            default: true
          }
        },
        required: ['content', 'format']
      }
    },
  • src/index.ts:405-407 (registration)
    Registration of BMAD tools (including bmad_parse_specification) in the main server by calling registerBMADTools and adding to toolDefinitions.
    if (this.config.services.bmad && this.bmadService) {
      const bmadTools = registerBMADTools(this.tools, this.bmadService);
      this.toolDefinitions.push(...bmadTools);
  • Core helper method implementing the specification parsing logic for different formats, task generation, agent assignment, and task validation.
    async parseSpecification(request: ParseSpecRequest): Promise<ParseSpecResponse> {
      const { content, format, options = { generateTasks: false, autoAssign: false, validate: false } } = request;
      
      let spec: ParsedSpec;
      
      try {
        switch (format) {
          case 'markdown':
            spec = await this.parseMarkdown(content);
            break;
          case 'yaml':
            spec = await this.parseYAML(content);
            break;
          case 'plain':
            spec = await this.parsePlainText(content);
            break;
          default:
            throw new Error(`Unsupported format: ${format}`);
        }
    
        let tasks: Task[] = [];
        let assignments: Assignment[] = [];
        let validation: ValidationResult[] = [];
    
        if (options.generateTasks) {
          tasks = await this.generateTasks(spec);
          this.tasks.push(...tasks);
        }
    
        if (options.autoAssign && tasks.length > 0) {
          assignments = await this.assignTasks(tasks);
          this.assignments.push(...assignments);
        }
    
        if (options.validate && tasks.length > 0) {
          validation = await this.validateTasks(tasks);
        }
    
        return {
          spec,
          tasks,
          assignments,
          validation: validation.length > 0 ? validation : undefined
        };
    
      } catch (error: any) {
        throw new Error(`Failed to parse specification: ${error.message}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions parsing and task generation but doesn't disclose behavioral traits such as whether this is a read-only operation, if it modifies data, error handling, performance characteristics, or side effects. For a tool with 5 parameters and no annotations, this is a significant gap.

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

Conciseness5/5

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

The description is a single, efficient sentence: 'Parse a business specification document and generate tasks.' It's front-loaded with the core purpose and has zero waste, making it easy to understand quickly.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns, how tasks are generated, or any behavioral context. For a parsing and generation tool, more detail 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. The description adds no additional meaning beyond what's in the schema, such as explaining the relationship between parameters or providing usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the tool's purpose: 'Parse a business specification document and generate tasks.' It specifies the verb ('parse') and resource ('business specification document'), and mentions the output ('generate tasks'). However, it doesn't distinguish this from sibling tools like 'analyze_document_quality' or 'generate_documentation_report', which might 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions. With siblings like 'analyze_document_quality' and 'generate_documentation_report', there's no indication of how this tool differs or when it's preferred.

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/Ghostseller/CastPlan_mcp'

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