Skip to main content
Glama

Identify Champions

impact_identify_champions
Read-only

Identify likely champion, economic buyer, and other buying-committee roles from your product and problem, plus anti-champion warning signs and a champion development path.

Instructions

Helps you decide who inside the buyer will push for you. You give what your product does and the problem it solves, plus optional company name, target company type, price point and sector. You get hypotheses for the champion, the economic buyer, the technical influencer, commercial and control reviewers and daily users, warning signs of an anti champion, a path to develop the champion and what to give them. These are roles to test, not named people. 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 buyer_group_analyzer when you need champion-role hypotheses from a product and problem.

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>",
      "problem_solved": "<problem_solved>"
    },
    "name": "impact_identify_champions"
  }
}

Input Schema

NameRequiredDescriptionDefault
price_pointNoWhat you charge, with the period, in your own words (for example "$50,000 a year" or "$3,750 per month"). 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".
company_nameNoYour company name. Format is text. For example, "invoice review service".
problem_solvedYesThe core problem you solve. Format is text. For example, "invoice exceptions delay month-end close".
product_descriptionYesWhat your product does (1-2 sentences). Format is text. For example, "checks invoice exceptions before approval".
target_company_typeNoType of companies you target (e.g., "mid-size fintech companies", "enterprise manufacturers"). Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.2.28
    • 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 / price_point / description
      Previous value: -"Optional: ACV range (e.g., \"$50K-100K\")"New value: +"What you charge, with the period, in your own words (for example \"$50,000 a year\" or \"$3,750 per month\"). Format is text."
    • changedInput schema / properties / problem_solved / description
      Previous value: -"The core problem you solve"New value: +"The core 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 (1-2 sentences)"New value: +"What your product does (1-2 sentences). Format is text. For example, \"checks invoice exceptions before approval\"."
    • changedInput schema / properties / target_company_type / description
      Previous value: -"Type of companies you target (e.g., \"Series B SaaS\", \"Enterprise manufacturing\")"New value: +"Type of companies you target (e.g., \"mid-size fintech companies\", \"enterprise manufacturers\"). Format is text."
    • 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.4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description discloses that no sign-in is needed, no inputs or outputs are stored, only hosted usage metadata is recorded, and invalid or missing fields produce an error naming the field. These are genuinely additive operational facts, though return format and any rate/length limits are not covered.

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?

The output inventory and the role-hypothesis caveat are front-loaded and earn their space, and the closing sibling routing is well placed. The sentence enumerating inputs largely duplicates the schema's required/optional flags, which is the one mildly wasteful element.

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 no output schema, the description carries the full burden of describing returns, and it does so concretely by naming each buyer role and the supporting artifacts (anti-champion signals, development path, what to give them). Combined with the auth/storage/error disclosure, an agent has everything needed to call it correctly and interpret results.

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% and every parameter carries a description and example, so the schema does the heavy lifting. The description only restates which fields are required versus optional and lists them in prose, adding no new meaning such as how price point or sector influence the hypotheses. Baseline 3 applies.

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 opening sentence states a specific outcome (decide who inside the buyer will push for you) and the description enumerates the exact deliverables — champion, economic buyer, technical influencer, commercial and control reviewers, daily users, anti-champion warning signs, and a development path. It explicitly frames the output as role hypotheses rather than named people, which prevents a common misread.

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 names an alternative (buyer_group_analyzer) and the condition that selects this tool over it: when you need champion-role hypotheses derived from a product and problem statement. It also states the required inputs up front, so an agent knows the minimum to call it.

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