Skip to main content
Glama

Craft Message

impact_craft_message
Read-only

Turns your target customer, key benefit, and differentiation into a positioning statement, message hierarchy, audience versions, objection handling, and testing ideas.

Instructions

Helps you decide what your core message is, and how to test it. You give your target customer, the key benefit and what sets you apart, plus optional product name, customer need, category, main competitor and business model. You get a positioning statement (full and one sentence), a message hierarchy from tagline to three supporting pillars, versions for different audiences, objection handling and ways to test the message. It writes from your own words, in whole sentences. 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 impact_translate_execution when you need the core positioning statement and message hierarchy.

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": {
      "target_customer": "<target_customer>",
      "key_benefit": "<key_benefit>",
      "differentiation": "<differentiation>"
    },
    "name": "impact_craft_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorNoPrimary alternative/competitor. Format is text. For example, "the current manual review process".
key_benefitYesPrimary benefit/reason to buy. Format is text. For example, "resolve invoice exceptions before month-end".
your_sectorNoYour 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".
product_nameNoYour product name. Format is text. For example, "invoice review service".
customer_needNoThe need they have, written as an action (for example "lose days chasing low-risk cloud alerts"). Format is text.
business_modelNoHow you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose the cost and proof lines; read from your inputs when not given. Format is text using one of the listed labels. For example, "saas".
differentiationYesYour unique differentiation. Format is text. For example, "checks invoice exceptions before approval".
target_customerYesTarget customer description. Format is text. For example, "manufacturers with 200 to 500 employees".
product_categoryNoYour product category, written as a noun phrase (for example "cloud security monitoring platform"). Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.2.28
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose the cost and proof lines; read from your inputs when not given. Format is text using one of the listed labels. For example, \"saas\".",
      +  "enum": [
      +    "saas",
      +    "services",
      +    "connectivity",
      +    "transactions",
      +    "marketplace",
      +    "hardware_software",
      +    "investment"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / competitor / description
      Previous value: -"Primary alternative/competitor"New value: +"Primary alternative/competitor. Format is text. For example, \"the current manual review process\"."
    • changedInput schema / properties / customer_need / description
      Previous value: -"The need or opportunity they have"New value: +"The need they have, written as an action (for example \"lose days chasing low-risk cloud alerts\"). Format is text."
    • changedInput schema / properties / differentiation / description
      Previous value: -"Your unique differentiation"New value: +"Your unique differentiation. Format is text. For example, \"checks invoice exceptions before approval\"."
    • changedInput schema / properties / key_benefit / description
      Previous value: -"Primary benefit/reason to buy"New value: +"Primary benefit/reason to buy. Format is text. For example, \"resolve invoice exceptions before month-end\"."
    • changedInput schema / properties / product_category / description
      Previous value: -"Your product category"New value: +"Your product category, written as a noun phrase (for example \"cloud security monitoring platform\"). Format is text."
    • changedInput schema / properties / product_name / description
      Previous value: -"Your product name"New value: +"Your product name. Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / target_customer / description
      Previous value: -"Target customer description"New value: +"Target customer description. Format is text. For example, \"manufacturers with 200 to 500 employees\"."
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "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 observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description still adds real context beyond them: no sign-in required, no inputs or outputs stored, hosted usage metadata recorded, and that missing required fields or invalid values return an error naming what to supply or correct. It does not describe output format details, but the annotations carry the main behavioral burden.

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?

It is front-loaded with purpose, then moves through inputs, outputs, behavioral guarantees, error behavior and the alternative in a logical order, with every sentence carrying information. It is longer than strictly necessary and the input enumeration partly duplicates the schema, which keeps it below a 5.

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?

For a nine-parameter generation tool with no output schema, the description compensates by describing the shape of the returned deliverables in detail. Combined with the annotations covering safety and the 100%-covered input schema, an agent has everything needed to call this correctly and set expectations for the result.

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 every one of the nine parameters is already documented with format and examples. The description's parameter sentence enumerates the same fields and separates the three required from the six optional, but adds no meaning the schema does not already contain. Baseline 3 is appropriate.

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?

The description opens with a concrete verb+resource ('decide what your core message is, and how to test it') and then enumerates the actual deliverables: positioning statement (full and one-sentence), message hierarchy from tagline to three pillars, audience variants, objection handling and test methods. It also explicitly contrasts itself with impact_translate_execution, so an agent can separate the two 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 Guidelines4/5

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

It names a specific alternative and the condition that selects this tool: 'Use this instead of impact_translate_execution when you need the core positioning statement and message hierarchy.' That is clear routing guidance. It stops short of stating when this tool is the wrong choice in other situations, so it is not a full when/when-not treatment.

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