Skip to main content
Glama

Launch Commander

launch_commander
Read-only

Creates a phased launch plan with tasks, messaging, and success metrics from your product, launch type, target segments, and goals; accepts dates, quarters, or TBD.

Instructions

Helps you decide your launch plan: it takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and messaging follow the sector and business model read from your inputs, and each goal is filed under its own metric. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of craft_gtm_analyzer when you need to create a launch plan from a product, segments and goals.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_feature": "<product_feature>",
      "launch_type": "<launch_type>",
      "target_segments": "<target_segments>",
      "goals": "<goals>"
    },
    "name": "launch_commander"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsYesLaunch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers'). Format is text.
industryNoOptional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, "logistics_tech".
team_sizeNoMarketing/GTM team size affects task distribution. Format is text using one of the listed labels. For example, "solo".
launch_dateNoTarget launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode. Format is text in YYYY-MM-DD form. For example, "2026-11-17".
launch_typeYesType of launch determines plan complexity. Format is text using one of the listed labels. For example, "major_release".
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
budget_levelNoBudget affects recommended tactics. Format is text using one of the listed labels. For example, "bootstrap".
business_modelNoOptional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas".
product_featureYesWhat you're launching (product/feature name and description). Format is text. For example, "invoice review service".
target_segmentsYesTarget customer segments (comma-separated). Format is text. For example, "manufacturers with 200 to 500 employees".
available_channelsNoOptional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'. Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.2.25
    • addedInput schema / properties / available_channels
      Added value: +{
      +  "description": "Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'. Format is text.",
      +  "type": "string"
      +}
    • removedInput schema / properties / budget
      Removed value: -{
      -  "description": "Available budget",
      -  "type": "string"
      -}
    • addedInput schema / properties / budget_level
      Added value: +{
      +  "description": "Budget affects recommended tactics. Format is text using one of the listed labels. For example, \"bootstrap\".",
      +  "enum": [
      +    "bootstrap",
      +    "moderate",
      +    "well_funded"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, \"saas\".",
      +  "enum": [
      +    "saas",
      +    "services",
      +    "connectivity",
      +    "transactions",
      +    "marketplace",
      +    "hardware_software",
      +    "investment"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / channels
      Removed value: -{
      -  "description": "Available channels: marketing, sales, PR, partners",
      -  "type": "string"
      -}
    • changedInput schema / properties / goals / description
      Previous value: -"Launch objectives and success metrics"New value: +"Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers'). Format is text."
    • addedInput schema / properties / industry
      Added value: +{
      +  "description": "Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / launch_date / description
      Previous value: -"Target launch date"New value: +"Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode. Format is text in YYYY-MM-DD form. For example, \"2026-11-17\"."
    • addedInput schema / properties / launch_type
      Added value: +{
      +  "description": "Type of launch determines plan complexity. Format is text using one of the listed labels. For example, \"major_release\".",
      +  "enum": [
      +    "major_release",
      +    "feature_launch",
      +    "beta_launch",
      +    "product_update",
      +    "market_expansion"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / product_feature / description
      Previous value: -"Product/feature being launched"New value: +"What you're launching (product/feature name and description). Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / target_segments / description
      Previous value: -"Primary and secondary audience segments"New value: +"Target customer segments (comma-separated). Format is text. For example, \"manufacturers with 200 to 500 employees\"."
    • removedInput schema / properties / team
      Removed value: -{
      -  "description": "Team members and roles",
      -  "type": "string"
      -}
    • addedInput schema / properties / team_size
      Added value: +{
      +  "description": "Marketing/GTM team size affects task distribution. Format is text using one of the listed labels. For example, \"solo\".",
      +  "enum": [
      +    "solo",
      +    "small_2_5",
      +    "medium_6_15",
      +    "large_15_plus"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "product_feature",
      -  "launch_date",
      -  "target_segments",
      -  "goals"
      -]New value: +[
      +  "product_feature",
      +  "launch_type",
      +  "target_segments",
      +  "goals"
      +]
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, and the description goes well beyond them: no sign-in, no stored inputs or outputs, hosted usage metadata recorded, read-only for business data, and error behavior that names the missing or invalid field. It also discloses the return artifacts and the inference fallback for optional sector fields, which is exactly the kind of context annotations cannot carry.

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?

Front-loaded with purpose and output, then usage routing, then behavioral/privacy facts; no filler sentences. It is dense for a single paragraph, but every sentence carries information an agent needs before invoking it.

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

Completeness4/5

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

For an 11-parameter tool with no output schema, it covers inputs, return artifacts, error behavior and data handling, which is nearly everything needed. The only gap is not resolving why both industry and your_sector exist or how they interact when both are supplied.

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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining that 'TBD' or a quarter yields a flexible plan and that omitted sector/business model are inferred from other inputs and reported back. It does not clarify the apparent overlap between the optional industry and your_sector fields, which is the main remaining ambiguity in an 11-parameter tool.

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

Purpose5/5

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

States a concrete verb and artifact: takes product, launch type, segments and goals and returns a phased launch plan with tasks, a messaging table and success metrics. It also names the sibling it is not (craft_gtm_analyzer), so an agent can distinguish it without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Use this instead of craft_gtm_analyzer when you need to create a launch plan from a product, segments and goals." It also gives the condition that selects planning mode (a date, or 'TBD'/quarter) rather than leaving it to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.