Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Win/Loss Analyzer

win_loss_analyzer
Read-only

Analyze why a deal was won or lost and what to change, turning deal details or patterns into buyer-reason insights, review questions, and sector notes.

Instructions

Helps you decide why you won or lost and what to change. You give the details of one deal, a competitor pattern or a set of deals. You get a short write up that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then questions for the review call and sector notes. It adds no figure or reason you did not give, and says what a missing outcome or reason would add. 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 deal_strategy_coach when you need to learn from completed outcomes and stated buyer reasons.

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": {
      "analysis_type": "<analysis_type>"
    },
    "name": "win_loss_analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_valueNoDeal value. Format is a JSON number. For example, 12.
loss_reasonNoStated loss reason (for lost deals). Format is text. For example, "two deals paused after budget review".
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".
deal_detailsNoDeal details, can be rough notes, CRM export, or structured data. Format is text. For example, "renewal was paused because budget approval was delayed".
deal_outcomeNoDeal outcome for single deal analysis. Format is text using one of the listed labels. For example, "won".
analysis_typeYesType of analysis. Format is text using one of the listed labels. For example, "single_deal".
your_solutionNoWhat you were selling. Format is text. For example, "invoice review service".
competitor_wonNoCompetitor who won (if applicable). Format is text. For example, "the current manual review process".
multiple_dealsNoFor portfolio analysis: summary of multiple deals. Format is text. For example, "renewal was paused because budget approval was delayed".
sales_cycle_daysNoLength of sales cycle. Format is a JSON number. For example, 12.
stakeholders_involvedNoKey stakeholders and their positions. Format is text. For example, "procurement lead and security reviewer".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.2.33
    • changedInput schema / properties / analysis_type / description
      Previous value: -"Type of analysis"New value: +"Type of analysis. Format is text using one of the listed labels. For example, \"single_deal\"."
    • changedInput schema / properties / competitor_won / description
      Previous value: -"Competitor who won (if applicable)"New value: +"Competitor who won (if applicable). Format is text. For example, \"the current manual review process\"."
    • changedInput schema / properties / deal_details / description
      Previous value: -"Deal details - can be rough notes, CRM export, or structured data"New value: +"Deal details, can be rough notes, CRM export, or structured data. Format is text. For example, \"renewal was paused because budget approval was delayed\"."
    • changedInput schema / properties / deal_outcome / description
      Previous value: -"Deal outcome for single deal analysis"New value: +"Deal outcome for single deal analysis. Format is text using one of the listed labels. For example, \"won\"."
    • changedInput schema / properties / deal_value / description
      Previous value: -"Deal value"New value: +"Deal value. Format is a JSON number. For example, 12."
    • addedInput schema / properties / deal_value / minimum
      Added value: +0
    • changedInput schema / properties / loss_reason / description
      Previous value: -"Stated loss reason (for lost deals)"New value: +"Stated loss reason (for lost deals). Format is text. For example, \"two deals paused after budget review\"."
    • changedInput schema / properties / multiple_deals / description
      Previous value: -"For portfolio analysis: summary of multiple deals"New value: +"For portfolio analysis: summary of multiple deals. Format is text. For example, \"renewal was paused because budget approval was delayed\"."
    • changedInput schema / properties / sales_cycle_days / description
      Previous value: -"Length of sales cycle"New value: +"Length of sales cycle. Format is a JSON number. For example, 12."
    • addedInput schema / properties / sales_cycle_days / minimum
      Added value: +0
    • changedInput schema / properties / stakeholders_involved / description
      Previous value: -"Key stakeholders and their positions"New value: +"Key stakeholders and their positions. Format is text. For example, \"procurement lead and security reviewer\"."
    • 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: -"What you were selling"New value: +"What you were selling. Format is text. For example, \"invoice review service\"."
  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?

Beyond the readOnlyHint/destructiveHint/openWorldHint annotations, it discloses that it adds no figure or reason not supplied, flags what a missing outcome or reason would contribute, requires no sign-in, stores no inputs or outputs, records hosted usage metadata, and returns errors naming what to supply or correct. That is substantial behavioral context an agent cannot get from the annotations alone.

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?

Sentences are front-loaded: purpose and scope first, then output contents, then behavioral guarantees, then the sibling routing rule. Nearly every sentence carries distinct information, though the sign-in/storage/metadata trio is slightly list-like and could be compressed.

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, no-output-schema analytical tool, the description covers what comes back (write-up sections), the analysis modes, privacy and authentication posture, and error behavior. An agent has enough to call it correctly and set expectations for the response shape.

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 enums are documented per field, so the structured data carries parameter meaning. The description adds only a loose mapping ('details of one deal, a competitor pattern or a set of deals') without naming analysis_type values or field-level constraints, so baseline 3 is appropriate.

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 opens with a specific verb and resource: 'decide why you won or lost and what to change', then enumerates the accepted input shapes (one deal, a competitor pattern, a set of deals) and the produced artifact (a short write-up naming outcome, buyer-stated reason, implication, review-call questions, sector notes). It also explicitly distinguishes itself from deal_strategy_coach, so an agent can route correctly without opening a schema.

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 alternative and the selecting condition: 'Use this instead of deal_strategy_coach when you need to learn from completed outcomes and stated buyer reasons.' The input-shape sentence further implies which analysis modes are in scope, leaving little to inference.

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