Skip to main content
Glama

CRAFT GTM Analyzer

craft_gtm_analyzer
Read-only

Scores a GTM document against CRAFT dimensions, shows the plan's own text for each, and names missing elements plus sections to add, so you can decide whether it is clear enough to run.

Instructions

Helps you decide whether a GTM plan is clear enough to run: it takes the text of a GTM document or plan and returns a score for each CRAFT dimension, based only on what the plan contains. Timeline counts real dates, durations and quarters; the answer shows the plan's own line for each dimension, names only the elements that are missing and suggests sections to add. 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 launch_commander when you already have a GTM document to assess against CRAFT.

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": {
      "document_content": "<document_content>",
      "document_type": "<document_type>"
    },
    "name": "craft_gtm_analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
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".
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".
document_typeYesType of document (shown in the analysis). Format is text using one of the listed labels. For example, "gtm_strategy".
desired_outcomeNoOptional: What action should this document drive. Format is text. For example, "resolve invoice exceptions before month-end".
document_contentYesThe GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework. Format is text. For example, "Launch invoice review services for manufacturers over six weeks, with a finance owner and weekly exception reviews.".
intended_audienceNoOptional: Who will read/approve this document. Format is text. For example, "finance leaders at manufacturers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.2.25
    • changedInput schema / properties / desired_outcome / description
      Previous value: -"What it should achieve"New value: +"Optional: What action should this document drive. Format is text. For example, \"resolve invoice exceptions before month-end\"."
    • changedInput schema / properties / document_content / description
      Previous value: -"Strategy document to analyze"New value: +"The GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework. Format is text. For example, \"Launch invoice review services for manufacturers over six weeks, with a finance owner and weekly exception reviews.\"."
    • changedInput schema / properties / document_type / description
      Previous value: -"Type: GTM plan, launch plan, positioning"New value: +"Type of document (shown in the analysis). Format is text using one of the listed labels. For example, \"gtm_strategy\"."
    • addedInput schema / properties / document_type / enum
      Added value: +[
      +  "gtm_strategy",
      +  "launch_plan",
      +  "campaign_brief",
      +  "quarterly_plan",
      +  "project_proposal",
      +  "marketing_plan"
      +]
    • 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 / intended_audience / description
      Previous value: -"Who will use this document"New value: +"Optional: Who will read/approve this document. Format is text. For example, \"finance leaders at manufacturers\"."
    • 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"
      +}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description discloses the privacy profile (no sign-in, no input or output storage, usage metadata recorded) and the failure mode ('missing required fields or invalid values return an error naming what to supply'). It also previews answer shape: the plan's own line per dimension, missing elements named only, section suggestions added.

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, then output shape, then behavioral constraints, then the alternative — a sensible order with little filler. It is on the long side for a single paragraph and the 'Read-only for business data' and 'stores no inputs or outputs' clauses overlap slightly with the readOnlyHint annotation.

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

Completeness5/5

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

With six parameters, no output schema, and a scoring tool whose return shape matters, the description compensates by explaining what the answer contains (per-dimension scores, verbatim plan lines, named gaps, suggested sections). Nothing an agent needs to decide to call it or to interpret the result is missing.

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 parameter meaning is already carried by the schema and the baseline of 3 applies. The description adds one real semantic detail ('Timeline counts real dates, durations and quarters') about how a dimension is computed, but it does not clarify the overlapping `industry` versus `your_sector` parameters, which read almost identically in the schema.

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 specific verb and resource ('takes the text of a GTM document or plan and returns a score for each CRAFT dimension') and defines the evaluation basis ('based only on what the plan contains'). It also names the sibling it replaces, so the tool is distinguishable from launch_commander 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?

'Use this instead of launch_commander when you already have a GTM document to assess against CRAFT' gives an explicit alternative plus the selecting condition. The converse (no document on hand → use launch_commander) follows directly, so no inference about routing is left to the agent.

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