Launch Engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASSET_FACTORY_PROJECT_DIR | No | Path to the project directory. If not set, defaults to current working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scoutB | Preliminary market scanning. Takes a raw idea and determines if it's worth deeper investigation. |
| autonomyA | Agent Autonomy Score — scores a market across 7 dimensions for AI-buildable product viability. |
| market_intelB | Market Intelligence OS — deep market research with competitive analysis and scoring. |
| researchB | Therapeutic Buyer Engine — deep buyer persona research with 25-35 web searches. |
| build_blocksC | 3-Part Promotion Invention — builds the 7 Building Blocks from buyer research. |
| stress_testA | Offer Stress Test — scores the offer across 10 dimensions, returns GO/REVISE/REBUILD. |
| unit_economicsA | Unit Economics Gate — models CPA, LTV, break-even, and budget requirements. |
| name_lockC | Name Lock Gate — locks the business/product name before any assets are built. |
| platformA | Platform Engine — scores and selects the tech stack for product delivery. |
| productB | Product Architecture Engine — designs the product/service delivery structure. |
| deployC | Campaign Deployment Engine — generates sales pages, email sequences, and ad copy. |
| qaB | Persona Alignment Gate — 7-check QA ensuring all copy aligns with buyer persona. |
| validate_prepB | Validation Deployment Package — generates the deployment checklist for real-world testing. |
| validate_checkB | Daily 60-Second Health Check — quick metrics review during validation window. |
| validate_decideB | Validation Verdict Engine — end-of-window decision: ADVANCE, ITERATE, or KILL. |
| feedbackB | Optimizer Feedback Loop — diagnoses performance issues and routes fixes. |
| traffic_strategyC | Traffic Strategy Engine — researches and scores traffic channels. |
| channelsC | Channel Deployment Engine — sets up and configures selected traffic channels. |
| creative_testC | Creative Testing Protocol — generates and manages ad creative variations. |
| funnel_optimizeC | Funnel Optimization Engine — CRO testing across the conversion funnel. |
| scaleC | Scale Protocol — systematic scaling of validated traffic channels. |
| traffic_analyticsC | Traffic Analytics & Attribution — performance reporting and attribution. |
| dream_100C | Dream 100 Relationship Strategy — entity discovery and outreach sequences. |
| passive_deployC | Passive Asset Deployment Agent (PADA) — marketplace asset scoring and build specs. |
| passive_checkB | Passive Asset Validation Check — scheduled performance checks at Day 14/30/45/60/90. |
| passive_compoundC | Anchor Compounding Engine — deploys related assets around proven anchors. |
| passive_portfolioB | Portfolio Feedback Report — quarterly review of all passive assets. |
| rapid_testA | Rapid Idea Test — compressed research + landing page + ads in a single pass. |
| rapid_checkC | Rapid Test Daily Check — reviews metrics against decision thresholds. |
| rapid_graduateB | Graduate Rapid Test to Full Pipeline — creates pipeline entry from rapid test data. |
| rapid_statusA | Rapid Test Portfolio Status — dashboard of all active/graduated/killed rapid tests. |
| content_engineB | Organic Content & SEO/GEO Engine — topic cluster research, pillar/spoke content generation, schema markup, AI visibility baselines. |
| content_repurposeA | Single-Pass Content Repurposing — takes one pillar page and generates 7+ platform-native assets (YouTube, short-form, Reddit, LinkedIn, newsletters, social). |
| seo_checkA | Monthly SEO/GEO Audit — content health, AI citation tracking, competitive gaps, technical SEO, content freshness scoring. |
| tournamentA | Parallel Portfolio Tournament — batch-evaluates 3-5 business ideas through Layer 1 simultaneously with comparison gates. ~50-60% faster than sequential scout runs. |
| statusA | Pipeline Status Report — shows current pipeline stage, completed steps, and next actions. |
| daily_checkB | Daily Operations Pulse — 5-minute daily check for any stage with live campaigns. |
| lessonsC | Pattern Library & Learnings Engine — capture and retrieve patterns across pipelines. |
| voice_extractB | Brand Voice Extraction — generates brand voice calibration docs from QA-passed content. |
| bold_actionB | Bold Action Playbook — identifies the single highest-leverage irreversible move for credibility compression and ICP surface area expansion. |
| portfolio_triageA | Portfolio Triage — ranks all pipelines past unit-economics by Profit Velocity Score and enforces active pipeline cap. |
| revenue_reviewC | Weekly Revenue Review — compares actual revenue vs projections for selected pipelines and manages revenue phase transitions. |
| update_pipeline_stateB | Update pipeline-state.json. Use dot-notation paths to set values. Can create new pipelines and rapid tests. |
| save_assetA | Save a file to the assets/[market-name]/ directory. Use for all pipeline outputs: research, building blocks, copy, campaigns, etc. |
| capture_learningA | Capture a reusable learning/pattern to learnings.json. Called after key decisions, verdicts, and pipeline milestones. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 45 tools
Most tools have distinct purposes and descriptions that clearly separate them, such as the passive_* and rapid_* groups. Some potential overlap exists (e.g., research vs. market_intel, scout vs. tournament), but descriptions sufficiently differentiate them.
Names use consistent snake_case and are descriptive. However, there is a mix of noun-first (e.g., content_engine, market_intel) and verb-first (e.g., build_blocks, save_asset) patterns, which is a minor inconsistency but still predictable.
With 45 tools, the server is overloaded. This far exceeds the typical well-scoped range (3-15) and is likely to overwhelm agents, leading to inefficiency and selection difficulty.
The tool set covers the full lifecycle of a marketing launch pipeline from ideation, research, product, content, campaigns, validation, optimization, scaling, to ongoing monitoring and learning. No obvious gaps are present.