Skip to main content
Glama

Competitive Intel

competitive_intel
Read-only

Generates one battle card per named competitor from your product details, strengths, weaknesses, objections, wins, and losses so teams know how to win each deal.

Instructions

Helps you decide how to win against each competitor: it takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses stay in your own words. 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_trap_setter when you need complete battle cards across the competitors you supply.

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>",
      "competitors": "<competitors>"
    },
    "name": "competitive_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoOptional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, "logistics_tech".
competitorsYesCompetitor names, comma-separated. You get one battle card for each competitor named. Format is text. For example, "the current manual review process".
recent_winsNoWhy customers chose you over competitors: used as your strengths when none are given. Format is text. For example, "finance teams chose the documented exception 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".
your_productYesYour product name and brief description. Format is text. For example, "invoice review service".
recent_lossesNoWhy you lost deals to competitors: used as your gaps when none are given. Format is text. For example, "two deals paused after budget review".
business_modelNoOptional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas".
your_strengthsNoOptional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided. Format is text. For example, "checks invoice exceptions before approval".
your_weaknessesNoOptional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided. Format is text. For example, "handoffs require manual reconciliation".
common_objectionsNoSales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'. Format is text.
competitor_detailsNoOptional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names. Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv2.2.25
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. 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 / common_objections / description
      Previous value: -"Objections in competitive deals"New value: +"Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'. Format is text."
    • addedInput schema / properties / competitor_details
      Added value: +{
      +  "description": "Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names. Format is text.",
      +  "type": "string"
      +}
    • changedInput schema / properties / competitors / description
      Previous value: -"3-5 key competitors (comma-separated)"New value: +"Competitor names, comma-separated. You get one battle card for each competitor named. Format is text. For example, \"the current manual review process\"."
    • addedInput schema / properties / industry
      Added value: +{
      +  "description": "Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. 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"
      +}
    • removedInput schema / properties / market
      Removed value: -{
      -  "description": "Target market",
      -  "type": "string"
      -}
    • addedInput schema / properties / recent_losses
      Added value: +{
      +  "description": "Why you lost deals to competitors: used as your gaps when none are given. Format is text. For example, \"two deals paused after budget review\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / recent_wins
      Added value: +{
      +  "description": "Why customers chose you over competitors: used as your strengths when none are given. Format is text. For example, \"finance teams chose the documented exception process\".",
      +  "type": "string"
      +}
    • removedInput schema / properties / your_differentiators
      Removed value: -{
      -  "description": "Your unique value propositions",
      -  "type": "string"
      -}
    • changedInput schema / properties / your_product / description
      Previous value: -"Your product name and description"New value: +"Your product name and brief description. Format is text. For example, \"invoice review service\"."
    • 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"
      +}
    • addedInput schema / properties / your_strengths
      Added value: +{
      +  "description": "Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided. Format is text. For example, \"checks invoice exceptions before approval\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / your_weaknesses
      Added value: +{
      +  "description": "Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided. Format is text. For example, \"handoffs require manual reconciliation\".",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "your_product",
      -  "market",
      -  "competitors",
      -  "your_differentiators"
      -]New value: +[
      +  "your_product",
      +  "competitors"
      +]
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: no sign-in required, inputs and outputs are not stored, hosted usage metadata is recorded, and invalid or missing fields return an error naming what to supply. The read-only claim is consistent with readOnlyHint=true and destructiveHint=false rather than contradicting it.

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 is front-loaded in the first clause and the remaining sentences cover output shape, data handling, and error behavior without filler. A few clauses restate what the schema already documents (wins-to-strengths fallback appears in both), so it is slightly longer than strictly necessary.

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 an 11-parameter tool with no output schema, the description compensates well: it describes the returned artifact and its sections, the fallback behavior when optional inputs are omitted, the no-auth/no-retention posture, and the error contract. Nothing an agent needs to decide whether and how to call it is missing.

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 baseline is 3, and the description still adds real routing semantics: each competitor detail is routed to the competitor it names, each objection gets its own answer, and strengths/gaps fall back to wins/losses in the user's own words. It does not explain the distinction between the two overlapping sector fields (industry vs your_sector) or the business_model enum's effect on output.

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?

States a specific verb and outcome (decide how to win against each competitor) plus concrete inputs (your product, named competitors) and a concrete output (one battle card per competitor assembled from strengths, weaknesses, competitor details, objections, wins and losses). An agent can tell exactly what this produces without opening the schema.

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?

Explicitly names an alternative (competitive_trap_setter) and the selecting condition: use this one when you need complete battle cards across the competitors supplied. There is no when-not-to-use guidance beyond that single contrast, and the named alternative is not in the sibling list, but the routing intent is clear.

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