revenue-enablement-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_plan_builderA | Helps you decide how to grow an account in the next 90 days. You give the account name, plus contacts, products, threats and notes if you have them. You get a strategic account plan: a power map with one row per contact you name, whitespace analysis, competitive questions, an answer for each objection and a 90 day plan. It does not look the account up. 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 an account-wide 90-day growth plan spanning contacts and products. |
| deal_strategy_coachA | Helps you decide what to do next to move a deal. You give the deal name and stage, plus competitors, stakeholder positions and blockers. You get a deal health score, a strategy for the stage, next steps and risks to handle. Ask the user to confirm blocker status, economic buyer engagement, incumbent status and project status when those facts affect the score; typed facts take precedence over text. 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 mutual_action_plan_generator when you need to diagnose deal health and choose the next move. |
| discovery_question_bankA | Helps you decide what to ask on a discovery call. You give the framework you use (MEDDPICC, BANT, SPICED, Challenger, Gap Selling or all five) and what you already know about the prospect. You get an opening for the conversation, questions in the language of the prospect's sector and on what your solution covers, questions for each part of the framework, a closing and what to say to an objection. It uses only the inputs you give and says which it did not get. 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 customer_interview_kit when you need sales qualification questions for a live opportunity. |
| roi_business_case_builderA | Helps you decide how to build an ROI case the buyer's finance team can check. You give your solution, its main value driver and the buyer's own figures: an annual value estimate, or current annual cost with the expected improvement percent. With them you get the ROI, payback, three year value and sensitivity. Without them it shows no ROI: it names the inputs to add and gives the structure of the case (the cost lines to price, your quoted results as reference points, the questions to ask). 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 pricing_negotiation_guide when you need a buyer-checkable financial case before negotiating terms. Ask finance for the cash-only annual benefit when an investment decision depends on cash. |
| mutual_action_plan_generatorA | Helps you decide what has to happen, by whom and when, for a deal to sign on time. You give the deal name and the target close date, plus the current stage, the buyer's champion, economic buyer and evaluators, known requirements and process steps if you have them. You get a close plan both sides can work from, with milestones, owners and dates. 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 dated milestones and owners for an agreed close target. |
| win_loss_analyzerA | 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. |
| proposal_section_writerA | Helps you decide what to write in one proposal section for a buyer. You give the section you need (such as an executive summary, solution overview or pricing justification), your solution, the buyer's challenges, your differentiators, pricing and success measures. You get that section in sentences built from your inputs, with sector notes. It invents no figure, customer or date, and says once which inputs were not given. 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 champion_enablement_kit when you need one seller-authored proposal section for the buyer. |
| email_sequence_generatorA | Helps you decide what to send, and when, to open or restart a conversation. You give the persona, stage and objective (prospecting, nurture, follow up or re engagement), plus your solution, the pain point, value proposition, proof and ask. You get each email with its subject, send day and body, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented. 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 sales_enablement_content when you need scheduled outreach emails with subjects and send days. |
| demo_script_builderA | Helps you decide what to show in a demo, and in what order. You give the demo type, the persona and the use case, plus the features you must show and the pains you name. You get a timed run from opening to close, with spoken lines and a step for each feature tied to the pains, then discussion, close and follow up lines and sector notes. The answer says where each step came from and what it did not get. 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 sales_enablement_content when you need a timed product demonstration tied to the use case. |
| pricing_negotiation_guideA | Helps you decide how to answer a discount request without giving away margin. You give the negotiation scenario, plus deal value, the discount asked, each side's leverage and who approves. You get a leverage assessment, a value based negotiation strategy, answers to common pushback and a discount approval framework. 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 roi_business_case_builder when you need responses and approval guidance for a discount discussion. Ask whether the user has authority to approve the proposed terms. |
| champion_enablement_kitA | Helps you decide what to give your champion to sell internally. You give the asset you need (an executive brief, internal business case, objection responses or presentation talking points), your solution, the customer's situation and the objections you expect. You get the asset in the champion's voice with the recommendation, answers to likely questions, the decision requested, a note on the reader and sector notes. It invents no figure or quote. 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 proposal_section_writer when you need an internal asset written in the champion's voice. |
| competitive_trap_setterA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a distinct primary output (account plan, deal diagnosis, discovery questions, ROI model, mutual action plan, win/loss review, proposal section, email sequence, demo script, negotiation guidance, champion asset, competitor traps), and descriptions explicitly state when to prefer one over another. Residual overlap remains in the content-generation cluster — proposal_section_writer vs champion_enablement_kit, and deal_strategy_coach vs mutual_action_plan_generator — but the 'use this instead of X' disambiguation lines largely resolve it.
All twelve names are snake_case noun phrases ending in an agent-noun (builder, coach, bank, generator, analyzer, writer, guide, kit, setter), giving a predictable <domain>_<object>_<agent> pattern across the whole set. No mixing of camelCase, verb-first, or ad-hoc styles.
Twelve tools sit squarely in the well-scoped 3-15 range, and each corresponds to a distinct revenue-enablement artifact rather than a trivial variation. Nothing looks padded or missing on count alone.
The surface covers the pre-sales lifecycle well: discovery, account planning, deal strategy, close planning, ROI, pricing, proposals, champion assets, demos, outreach, win/loss, and competitive positioning. Gaps are minor but real — competitive_trap_setter points to an absent competitive_intel tool, and there is no post-sale/onboarding or shared content-library operation; the tools are also explicitly stateless, so no update/delete lifecycle exists.