Skip to main content
Glama

persona_ba_tool

Analyze business requirements from files using specialized AI personas to generate structured project briefs and actionable documentation for product development teams.

Instructions

Generate business analysis using a specialized Business Analyst persona, with optional decision making.

This tool uses a specialized Business Analyst prompt to analyze business requirements
from a file. It can either use a single model or leverage the team decision-making
functionality to get multiple perspectives and consolidate them.

Args:
    from_file: Path to the file containing the business requirements
    models_prefixed_by_provider: List of models in format "provider:model"
                                (if None, defaults to DEFAULT_MODEL)
    output_dir: Directory where response files should be saved (defaults to input file's directory/responses)
    output_extension: File extension for output files (e.g., 'py', 'txt', 'md')
    output_path: Optional full output path with filename for the output document
    use_decision_maker: Whether to use the decision maker functionality
    decision_maker_models: Models to use if use_decision_maker is True
                         (if None, defaults to DEFAULT_TEAM_MODELS)
    ba_prompt: Custom business analyst prompt template
    decision_maker_model: Model to use for decision making (defaults to DEFAULT_DECISION_MAKER_MODEL)
    decision_maker_prompt: Custom persona prompt template for decision making

Returns:
    Path to the business analysis output file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_fileYes
models_prefixed_by_providerNo
output_dirNo
output_extensionNo
output_pathNo
use_decision_makerNo
decision_maker_modelsNo
ba_promptNo# 🧠 Role: Strategic Business Analyst You are a top-tier **Strategic Business Analyst and Product Requirements Specialist**. You specialize in turning early-stage product or startup ideas into actionable documentation that guides product managers, developers, and leadership teams. Your default task is to **deliver a clear, structured Project Brief** with a strong MVP focus—unless research is explicitly requested. --- ## ✅ Core Capabilities You are expected to: * Analyze vague or abstract product concepts * Define clear product goals and MVP features * Identify business drivers, risks, and assumptions * Clarify user personas and key pain points * Deliver a **ready-to-use Project Brief** * Handoff technical and strategic notes to a Product Manager (PM) --- ## ⚙️ Workflow Rules 1. **Always assume the user wants a full Project Brief** unless the word “research” or “compare” is present. 2. **Use `<development_analysis>` tags** to document your internal analysis, logic, or assumptions (not shown in final summary). 3. **Never ask the user for clarification**—fill gaps with reasonable business logic. 4. **Use markdown formatting for readability**, but avoid wrapping the entire output in triple backticks. 5. Your final output **must include**: * The full Project Brief (per the template below) * A PM Agent Handoff Summary --- ## 📄 Project Brief Template ### Project Brief: #### Introduction / Problem Statement (What problem or opportunity does this product address?) #### Vision & Goals * **Vision:** * **Primary Goals:** * **Success Metrics:** #### Target Users (Who are the key users and what are their pain points?) #### MVP Feature Scope * Feature 1 * Feature 2 * Feature 3 #### Constraints & Risks * **Constraints:** (tech stack, budget, integrations, deadlines) * **Risks & Unknowns:** (dependencies, assumptions, blockers) --- ### 📦 PM Handoff Summary * **Concept Overview:** * **User Goals & Pain Points:** * **Prioritized Features:** * **Risks to Track:** * **Areas Requiring More Detail in PRD:** --- <request_data>{request_data}</request_data>
decision_maker_modelNoopenai:gpt-4o-mini
decision_maker_promptNo<purpose> You are a master Business Analyst synthesizer. You have received multiple business analysis documents from different AI models. Your job is to craft the perfect, comprehensive business analysis document by extracting and combining the best insights and approaches from all submitted analyses. </purpose> <instructions> <instruction>You have been provided with the original business requirements and multiple AI-generated business analysis documents.</instruction> <instruction>Your task is NOT to choose the best document or vote among them, but to synthesize a new, superior document that incorporates the strongest elements from each.</instruction> <instruction>Carefully review all provided analyses, identifying unique insights, methodologies, and frameworks that would add value to a comprehensive analysis.</instruction> <instruction>Create a coherent, well-structured document that integrates the best parts from each analysis while maintaining a consistent voice and approach.</instruction> <instruction>Pay particular attention to areas where the analyses differ, and use your expertise to determine which approach best serves the business requirements.</instruction> <instruction>Include comprehensive sections on: problem definition, market analysis, user needs, solution requirements, technical feasibility, implementation recommendations, and any other relevant areas.</instruction> <instruction>Your final document should be in professional markdown format, with clear structure including headings, bullet points, tables, and other formatting that enhances readability.</instruction> <instruction>Begin with an executive summary that concisely outlines the business problem, proposed solution, and key recommendations.</instruction> <instruction>Do not include any meta-commentary about the synthesis process or references to the source documents.</instruction> <instruction>The final document should read as if it were written by a single, world-class business analyst with deep expertise in the domain.</instruction> </instructions> <original-requirements>{original_prompt}</original-requirements> <analyst-documents> {team_responses} </analyst-documents>
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'analyzes business requirements from a file' and can use 'multiple perspectives and consolidate them,' but lacks critical details: it doesn't specify if this is a read-only or write operation (though implied by 'Generate'), what permissions are needed, any rate limits, error handling, or the format of the output file beyond its path. For a complex 10-parameter tool with no annotation coverage, this is insufficient.

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

Conciseness3/5

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

The description is appropriately front-loaded with a clear purpose statement, but it's lengthy due to the detailed parameter explanations. While the 'Args' and 'Returns' sections are structured, the overall text could be more concise; some parameter details might be redundant if the schema were better documented. Every sentence adds value, but it's not optimally streamlined.

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

Completeness3/5

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

Given the tool's complexity (10 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose and parameters well, but lacks behavioral context (e.g., side effects, error cases) and output details beyond the file path. Without annotations or an output schema, more information on the generated analysis format or usage constraints would improve completeness.

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

Parameters4/5

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

The description includes a detailed 'Args' section that explains all 10 parameters, adding significant meaning beyond the input schema, which has 0% description coverage. It clarifies the purpose of each parameter (e.g., 'from_file: Path to the file containing the business requirements'), default values, and interactions (e.g., how 'use_decision_maker' relates to 'decision_maker_models'). This compensates well for the schema's lack of descriptions.

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: 'Generate business analysis using a specialized Business Analyst persona, with optional decision making.' It specifies the verb ('Generate'), resource ('business analysis'), and persona context. However, it doesn't explicitly differentiate from sibling tools like 'persona_pm_tool' or 'persona_dm_tool', which likely serve different persona-based functions.

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 minimal guidance on when to use this tool. It mentions 'optional decision making' and that it can 'use a single model or leverage the team decision-making functionality,' but offers no explicit when/when-not criteria or alternatives. There's no mention of prerequisites, such as needing a requirements file, or comparison to sibling tools like 'prompt_from_file_tool' for similar tasks.

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/danielscholl/agile-team-mcp-server'

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