Skip to main content
Glama

Translate Execution

impact_translate_execution
Read-only

Turns your positioning statement, target customer, and key benefit into channel-specific copy: website hero, LinkedIn posts, cold email sequence, sales deck outline, and demo script.

Instructions

Helps you decide how your positioning should read in each channel. You give a positioning statement, your target customer and the key benefit, plus optional channels, product name and business model. You get copy to edit: a website hero, a LinkedIn tagline and post drafts, a three email cold sequence, a sales deck outline and a 15 minute demo script, with calls to action that fit your business model and the order to work the channels in. 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_craft_message when you already have positioning and need channel-specific copy.

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

Input Schema

NameRequiredDescriptionDefault
channelsNoWhich channels to cover, from website, linkedin, cold_email, sales_deck and product_demo. Others are listed as not covered; with none, all five are covered. Format is a JSON array. For example, ["website"].
key_benefitYesPrimary benefit, written as an action (for example "fix critical exposures first"). Format is text.
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".
business_modelNoHow you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose calls to action and commercial terms; read from your inputs when not given. Format is text using one of the listed labels. For example, "saas".
target_customerYesTarget customer profile. Format is text. For example, "manufacturers with 200 to 500 employees".
positioning_statementYesYour core positioning statement. Format is text. For example, "Finance teams need a clear owner for each invoice exception.".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 calls to action and commercial terms; 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 / channels / description
      Previous value: -"Channels to optimize for (e.g., [\"website\", \"linkedin\", \"email\", \"sales_deck\"])"New value: +"Which channels to cover, from website, linkedin, cold_email, sales_deck and product_demo. Others are listed as not covered; with none, all five are covered. Format is a JSON array. For example, [\"website\"]."
    • addedInput schema / properties / channels / items / description
      Added value: +"Format is text. For example, \"website\"."
    • changedInput schema / properties / key_benefit / description
      Previous value: -"Primary benefit"New value: +"Primary benefit, written as an action (for example \"fix critical exposures first\"). Format is text."
    • changedInput schema / properties / positioning_statement / description
      Previous value: -"Your core positioning statement"New value: +"Your core positioning statement. Format is text. For example, \"Finance teams need a clear owner for each invoice exception.\"."
    • 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 profile"New value: +"Target customer profile. 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.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description goes well beyond that by disclosing that it needs no sign-in, stores no inputs or outputs, records hosted usage metadata, and returns an error naming missing required fields or invalid values. Those are real behavioral traits an agent cannot get from the structured fields.

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 dense and front-loaded: the deliverable list and the sibling routing rule come before the operational caveats. The enumeration of outputs is long but every item is informative; a slightly tighter grouping of the privacy/error sentences would earn 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 seven-parameter generation tool with no output schema, the description covers what the agent needs: inputs expected, what comes back, whether data is stored, and how failures manifest. Nothing material is missing, and the absence of an output schema is compensated by the explicit list of return artifacts.

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 parameter already carries its own description, enum labels and examples. The description only summarizes which inputs there are (positioning, target customer, key benefit plus optional channels, product name, business model) and even omits your_sector, so it adds little beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource – it turns a positioning statement into channel-specific copy and then enumerates the exact artifacts produced (website hero, LinkedIn tagline and posts, three-email sequence, deck outline, demo script). It also distinguishes itself from impact_craft_message by naming that sibling, so an agent can route correctly 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?

It gives an explicit routing rule: 'Use this instead of impact_craft_message when you already have positioning and need channel-specific copy.' That names both the alternative and the condition that selects this tool, leaving nothing to inference.

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