Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Competitive Trap Setter

competitive_trap_setter
Read-only

Generate discovery questions, evaluation criteria, reference questions, and commercial tactics to expose gaps in one named competitor using your supplied strengths and known weaknesses.

Instructions

Helps you decide which questions expose the gaps in your main competitor, without negative selling. You give the named competitor, your solution, your strengths and its weak points as you know them. You get the set up, discovery questions, criteria to establish, reference call questions, requirement and scenario traps, commercial terms and tactics for your stage, with sector notes. Every line comes from your inputs and the sector, and none from an invented fact about the competitor. 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 discovery questions and evaluation criteria for one competitor.

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": {
      "competitor": "<competitor>",
      "your_solution": "<your_solution>"
    },
    "name": "competitive_trap_setter"
  }
}

Input Schema

NameRequiredDescriptionDefault
trap_typeNoType of competitive positioning. Format is text using one of the listed labels. For example, "discovery_questions".
competitorYesPrimary competitor to position against. Format is text. For example, "the current manual review process".
your_sectorNoOptional: 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".
buyer_personaNoRole of key evaluator. Format is text. For example, "finance director".
your_solutionYesYour product/solution. Format is text. For example, "invoice review service".
business_modelNoOptional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out. Format is text using one of the listed labels. For example, "saas".
your_strengthsNoYour key differentiators. Format is text. For example, "checks invoice exceptions before approval".
buyer_prioritiesNoWhat the buyer cares most about. Format is text. For example, "renewal decision depends on a documented approval process".
evaluation_stageNoStage of competitive evaluation. Format is text using one of the listed labels. For example, "early".
competitor_weaknessesNoKnown competitor weaknesses. Format is text. For example, "handoffs require manual reconciliation".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.2.33
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out. 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 / buyer_persona / description
      Previous value: -"Role of key evaluator"New value: +"Role of key evaluator. Format is text. For example, \"finance director\"."
    • changedInput schema / properties / buyer_priorities / description
      Previous value: -"What the buyer cares most about"New value: +"What the buyer cares most about. Format is text. For example, \"renewal decision depends on a documented approval process\"."
    • changedInput schema / properties / competitor / description
      Previous value: -"Primary competitor to position against"New value: +"Primary competitor to position against. Format is text. For example, \"the current manual review process\"."
    • changedInput schema / properties / competitor_weaknesses / description
      Previous value: -"Known competitor weaknesses"New value: +"Known competitor weaknesses. Format is text. For example, \"handoffs require manual reconciliation\"."
    • changedInput schema / properties / evaluation_stage / description
      Previous value: -"Stage of competitive evaluation"New value: +"Stage of competitive evaluation. Format is text using one of the listed labels. For example, \"early\"."
    • changedInput schema / properties / trap_type / description
      Previous value: -"Type of competitive positioning"New value: +"Type of competitive positioning. Format is text using one of the listed labels. For example, \"discovery_questions\"."
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: 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_solution / description
      Previous value: -"Your product/solution"New value: +"Your product/solution. Format is text. For example, \"invoice review service\"."
    • changedInput schema / properties / your_strengths / description
      Previous value: -"Your key differentiators"New value: +"Your key differentiators. Format is text. For example, \"checks invoice exceptions before approval\"."
  2. First observedv1.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 sign-in requirements, that inputs and outputs are not stored, that hosted usage metadata is recorded, how grounding works (all lines derive from inputs and sector), and that invalid or missing fields return an error naming what to fix.

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?

Content is front-loaded with purpose, then outputs, then behavioral caveats, and most sentences carry useful information. Some sentences are dense run-ons that could be split, but there is little filler.

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 10-parameter tool with no output schema, the description still conveys what the response contains (setup, discovery questions, criteria, reference-call questions, traps, commercial terms, sector notes) and how failures behave. An agent has enough to invoke it correctly.

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 four enums are self-documenting, so the baseline is 3. The description restates the key inputs (competitor, solution, strengths, weaknesses) and clarifies that optional sector/business model are inferred when omitted, but adds no new semantics beyond the schema.

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 names a concrete function: producing discovery questions, criteria, traps, and tactics for a single named competitor, with an explicit scope constraint (one competitor, no invented facts). It also distinguishes itself from the sibling competitive_intel by stating the condition that selects this tool instead.

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 alternative and the trigger for choosing it ("Use this instead of competitive_intel when you need discovery questions and evaluation criteria for one competitor"), and enumerates the inputs to supply. It stops short of saying when not to use it, e.g. multi-competitor or non-competitive deals.

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