Skip to main content
Glama

Map Alternatives

impact_map_alternatives
Read-only

Map the alternatives buyers compare you with, including competitors, the status quo, and doing nothing, to identify where you can lead and get discovery questions.

Instructions

Helps you decide what buyers compare you with, and where you can lead. You give your product and its category, plus optional competitors, their weaknesses and your strengths. You get one card for each competitor you name, the status quo and doing nothing, where you can lead and discovery questions, with your sector's questions and objections. It uses only what you give and says what would sharpen the map. 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 competitive_intel when you need positioning against competitors, the current approach and doing nothing.

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": {
      "your_product": "<your_product>",
      "category": "<category>"
    },
    "name": "impact_map_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesYour product category (e.g., "cloud security monitoring", "last-mile delivery software"). Format is text.
competitorsNoList of competitor names, and the status-quo options your buyers use (for example "spreadsheets"). A description in brackets after a name is kept. Format is a JSON array.
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".
your_productYesWhat your product does. Format is text. For example, "invoice review service".
your_strengthsNoWhat you do better than competitors, one per line or separated by semicolons. Format is text. For example, "checks invoice exceptions before approval".
competitor_weaknessesNoKnown competitor weaknesses or customer complaints, one per line or separated by semicolons. A weakness that names a competitor is shown on its card. Format is text. For example, "handoffs require manual reconciliation".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.2.28
    • changedInput schema / properties / category / description
      Previous value: -"Your product category (e.g., \"Sales engagement\", \"Data platform\")"New value: +"Your product category (e.g., \"cloud security monitoring\", \"last-mile delivery software\"). Format is text."
    • changedInput schema / properties / competitor_weaknesses / description
      Previous value: -"Optional: Known competitor weaknesses or customer complaints"New value: +"Known competitor weaknesses or customer complaints, one per line or separated by semicolons. A weakness that names a competitor is shown on its card. Format is text. For example, \"handoffs require manual reconciliation\"."
    • changedInput schema / properties / competitors / description
      Previous value: -"List of competitor names"New value: +"List of competitor names, and the status-quo options your buyers use (for example \"spreadsheets\"). A description in brackets after a name is kept. Format is a JSON array."
    • addedInput schema / properties / competitors / items / description
      Added value: +"Format is text. For example, \"the current manual review process\"."
    • changedInput schema / properties / your_product / description
      Previous value: -"What your product does"New value: +"What your product does. Format is text. For example, \"invoice review service\"."
    • 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"
      +}
    • changedInput schema / properties / your_strengths / description
      Previous value: -"Optional: What you do better than competitors"New value: +"What you do better than competitors, one per line or separated by semicolons. Format is text. For example, \"checks invoice exceptions before approval\"."
  2. First observedv2.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, it discloses that no sign-in is needed, no inputs or outputs are stored, hosted usage metadata is recorded, only supplied data is used, and that errors name the missing or invalid field. Those are exactly the privacy, error and data-provenance traits an agent cannot get from annotations. 'Read-only for business data' mildly echoes the annotation but adds little harm.

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?

Front-loaded with the core purpose and sizing up at roughly 110 words, with nearly every sentence carrying distinct information (outputs, data handling, errors, alternative). The middle sentence combining outputs is cramped and slightly run-on, and 'Read-only for business data' partly duplicates the annotation, keeping it from 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?

With no output schema, the description fully covers what is returned: one card per named competitor plus status quo and doing nothing, lead areas, discovery questions, and sector-specific questions and objections. Combined with 100% schema coverage and clear data-handling/error behavior, an agent has everything needed to call and interpret this tool.

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 is already documented in detail, and the description mostly restates them (product, category, optional competitors, weaknesses, strengths). It adds minor value by signaling optionality of competitors/weaknesses/strengths and that only supplied data is used, but adds no syntax or interpretation guidance beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete outcome: mapping what buyers compare you with (competitors, status quo, doing nothing) plus where you can lead and discovery questions. It distinguishes itself from a named alternative, competitive_intel. It falls short of 5 only because the framing ('Helps you decide what buyers compare you with') is indirect rather than a crisp verb+resource statement.

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 explicitly names the alternative tool and the condition that selects this one: use this instead of competitive_intel when you need positioning against competitors, the current approach and doing nothing. The required inputs (product, category) versus optional ones (competitors, weaknesses, strengths) are also stated, giving the agent clear entry criteria.

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