Skip to main content
Glama

IMPACT Framework Guide

impact_get_framework
Read-only

Returns the IMPACT positioning method step by step with templates or checklists, optionally focused on one phase and tailored to your sector, to guide which positioning steps to run and in what order.

Instructions

Helps you decide which positioning steps to run, and in what order. You give nothing, or one IMPACT step to focus on and your sector. You get the IMPACT positioning method step by step (identify champions, map alternatives, pinpoint value, anchor in a market, craft the message, translate it to execution), with a template or checklist for each step; a focus step returns that step only, and your sector adds its buyer roles, measures and proof points. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. No input returns all six steps. Invalid focus_phase or sector choices return an error naming the allowed values. Use this instead of impact_full_audit when you need the IMPACT method and templates before applying it to a product.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "impact_get_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorNoYour sector in your own words (for example logistics tech, fintech, SaaS, vertical SaaS, AI native, IT services, telecom, software or cybersecurity). Adds how the six steps read in that sector. The same as your selected sector; your selected sector wins when both are given. Format is text.
focus_phaseNoSpecific phase to focus on (identify/map/pinpoint/anchor/craft/translate). Format is text using one of the listed labels. For example, "identify".
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".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.28
    • changedInput schema / properties / focus_phase / description
      Previous value: -"Optional: specific phase to focus on (identify/map/pinpoint/anchor/craft/translate)"New value: +"Specific phase to focus on (identify/map/pinpoint/anchor/craft/translate). Format is text using one of the listed labels. For example, \"identify\"."
    • addedInput schema / properties / sector
      Added value: +{
      +  "description": "Your sector in your own words (for example logistics tech, fintech, SaaS, vertical SaaS, AI native, IT services, telecom, software or cybersecurity). Adds how the six steps read in that sector. The same as your selected sector; your selected sector wins when both are given. Format is text.",
      +  "type": "string"
      +}
    • 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.5/5.0
Behavior5/5

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

The annotations already declare readOnlyHint and openWorldHint=false, but the description adds materially: no sign-in required, no inputs or outputs stored, hosted usage metadata recorded, an omitted focus_phase returns all six steps, a supplied focus_phase returns only that step, and invalid focus_phase/sector values produce an error naming the allowed values. That is auth, persistence, and error-behavior disclosure well beyond what the annotations provide.

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?

Purpose and the sibling alternative are front-loaded, and the six enumerated phases earn their place by making the focus_phase enum interpretable. The middle section is a dense run-on with semicolons ('You give nothing, or one IMPACT step to focus on and your sector') and the phase list partially duplicates the enum, costing some readability.

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?

With no output schema, the description correctly carries the burden of describing returns: the six steps plus a template or checklist each, sector-augmented content, and error behavior on invalid enums. The remaining gap is the ambiguity between the two sector parameters, which an agent must resolve from the schema rather than the description.

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 schema already documents all three parameters and their enums; the description nonetheless adds behavioral meaning: a focus step narrows the response to that step only, and the sector adds buyer roles, measures and proof points. It does not clarify the overlap between the free-text 'sector' and the enum 'your_sector' parameters, leaving the precedence rule to the schema text.

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 concrete verb and resource: it returns the IMPACT positioning method step by step, with a template or checklist per step, enumerating all six phases. It also distinguishes itself from the sibling impact_full_audit by framing itself as the method/templates rather than the applied audit.

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 gives an explicit routing rule: 'Use this instead of impact_full_audit when you need the IMPACT method and templates before applying it to a product,' and it frames the tool as deciding which positioning steps to run and in what order. The gap is that it never explains when to call a per-phase sibling (e.g., impact_identify_champions) instead of this tool with focus_phase set to 'identify'.

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