Skip to main content
Glama

IMPACT Full Audit

impact_full_audit
Read-only

Run a full positioning audit across all six IMPACT steps to see whether your positioning is working and what to fix first.

Instructions

Helps you decide whether your positioning is working and what to fix first. You give what your product does, your target customer and the problem you solve, plus optional company name, differentiation, competitors, current positioning, customer feedback and business model. You get a positioning audit: an input completeness score for each IMPACT step, the proof you already have, your current positioning checked in words, a recommended positioning with tagline options, a 30 day action plan and the measures to track. The score measures how complete your inputs are, not how strong your positioning is. 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 need a full positioning review across all six IMPACT steps.

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_description": "<product_description>",
      "target_customer": "<target_customer>",
      "problem_solved": "<problem_solved>"
    },
    "name": "impact_full_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorsNoMain competitors. Format is a JSON array. For example, ["the current manual review process"].
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".
company_nameNoYour company name. Format is text. For example, "invoice review service".
business_modelNoHow you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used in the plan; read from your inputs when not given. It does not change the score. Format is text using one of the listed labels. For example, "saas".
problem_solvedYesThe problem you solve. Format is text. For example, "invoice exceptions delay month-end close".
target_customerYesWho you serve. Format is text. For example, "manufacturers with 200 to 500 employees".
customer_feedbackNoWhat customers say about you. Format is text. For example, "The reviewer asked who owns unresolved exceptions.".
current_positioningNoYour current positioning statement or tagline. Format is text. For example, "manual invoice review".
key_differentiationNoWhat makes you unique. Format is text. For example, "checks invoice exceptions before approval".
product_descriptionYesWhat your product does. Format is text. For example, "checks invoice exceptions before approval".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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 in the plan; read from your inputs when not given. It does not change the score. 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 / company_name / description
      Previous value: -"Your company name"New value: +"Your company name. Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / competitors / description
      Previous value: -"Main competitors"New value: +"Main competitors. Format is a JSON array. For example, [\"the current manual review process\"]."
    • addedInput schema / properties / competitors / items / description
      Added value: +"Format is text. For example, \"the current manual review process\"."
    • changedInput schema / properties / current_positioning / description
      Previous value: -"Optional: Your current positioning statement or tagline"New value: +"Your current positioning statement or tagline. Format is text. For example, \"manual invoice review\"."
    • changedInput schema / properties / customer_feedback / description
      Previous value: -"Optional: What customers say about you"New value: +"What customers say about you. Format is text. For example, \"The reviewer asked who owns unresolved exceptions.\"."
    • changedInput schema / properties / key_differentiation / description
      Previous value: -"What makes you unique"New value: +"What makes you unique. Format is text. For example, \"checks invoice exceptions before approval\"."
    • changedInput schema / properties / problem_solved / description
      Previous value: -"The problem you solve"New value: +"The problem you solve. Format is text. For example, \"invoice exceptions delay month-end close\"."
    • changedInput schema / properties / product_description / description
      Previous value: -"What your product does"New value: +"What your product does. Format is text. For example, \"checks invoice exceptions before approval\"."
    • changedInput schema / properties / target_customer / description
      Previous value: -"Who you serve"New value: +"Who you serve. 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.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses no sign-in requirement, no storage of inputs or outputs, hosted usage metadata recording, and error behavior for missing or invalid fields. It also clarifies that the completeness score measures input coverage rather than positioning strength, which prevents misinterpretation of the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the decision it supports, then covers inputs, outputs, caveats, and the sibling alternative without wasted wording. Despite its length, every sentence carries information an agent needs.

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 ten-parameter audit tool with no output schema, the description fully describes the deliverables, privacy and authentication behavior, error handling, and score interpretation. Nothing essential for correct invocation 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 coverage is 100% and each parameter already documents its format, examples, and enum labels. The description adds a useful grouping of required versus optional inputs, but little meaning beyond what the schema already provides.

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: a positioning audit across all six IMPACT steps that helps decide whether positioning is working and what to fix first. It also names the sibling it is not, making the tool's purpose unambiguous.

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 need a full positioning review across all six IMPACT steps.' That tells the agent both the condition and the alternative.

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