Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Pricing Negotiation Guide

pricing_negotiation_guide
Read-only

Assess leverage and generate a value-based negotiation strategy, pushback responses, and discount approval guidance for pricing talks so you can answer discount requests without giving away margin.

Instructions

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.

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": {
      "scenario": "<scenario>"
    },
    "name": "pricing_negotiation_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioYesNegotiation scenario. Format is text using one of the listed labels. For example, "discount_request".
deal_valueNoCurrent deal value. Format is a JSON number. For example, 12.
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_leverageNoYour leverage points (unique features, timeline, etc.). Format is text. For example, "renewal decision depends on a documented approval process".
your_solutionNoYour product/solution. Named in the guide and used, with your leverage, to read the sector and how you charge. 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".
buyer_leverageNoBuyer leverage points (size, reference potential, etc.). Format is text. For example, "renewal decision depends on a documented approval process".
value_deliveredNoQuantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own. Format is text. For example, "200 to 500 employees".
competitor_priceNoCompetitor pricing if known. Format is text. For example, "USD 24000 per year".
decision_timelineNoWhen decision needs to be made. Format is text. For example, "six weeks".
approval_authorityNoWho has final approval on pricing. Format is text. For example, "commercial director approves discounts above 10%".
discount_requestedNoDiscount percentage requested. Format is a JSON number. For example, 12.
pricing_authority_statusNoOptional confirmed fact. Ask whether the user can approve this price or discount. Free-text role titles do not establish authority; unconfirmed authority holds commitment to terms. Format is text using one of the listed labels. For example, "authorized".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.2.33
    • changedInput schema / properties / approval_authority / description
      Previous value: -"Who has final approval on pricing"New value: +"Who has final approval on pricing. Format is text. For example, \"commercial director approves discounts above 10%\"."
    • 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_leverage / description
      Previous value: -"Buyer leverage points (size, reference potential, etc.)"New value: +"Buyer leverage points (size, reference potential, etc.). Format is text. For example, \"renewal decision depends on a documented approval process\"."
    • changedInput schema / properties / competitor_price / description
      Previous value: -"Competitor pricing if known"New value: +"Competitor pricing if known. Format is text. For example, \"USD 24000 per year\"."
    • changedInput schema / properties / deal_value / description
      Previous value: -"Current deal value"New value: +"Current deal value. Format is a JSON number. For example, 12."
    • addedInput schema / properties / deal_value / minimum
      Added value: +0
    • changedInput schema / properties / decision_timeline / description
      Previous value: -"When decision needs to be made"New value: +"When decision needs to be made. Format is text. For example, \"six weeks\"."
    • changedInput schema / properties / discount_requested / description
      Previous value: -"Discount percentage requested"New value: +"Discount percentage requested. Format is a JSON number. For example, 12."
    • addedInput schema / properties / discount_requested / minimum
      Added value: +0
    • addedInput schema / properties / pricing_authority_status
      Added value: +{
      +  "description": "Optional confirmed fact. Ask whether the user can approve this price or discount. Free-text role titles do not establish authority; unconfirmed authority holds commitment to terms. Format is text using one of the listed labels. For example, \"authorized\".",
      +  "enum": [
      +    "authorized",
      +    "not_authorized",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / scenario / description
      Previous value: -"Negotiation scenario"New value: +"Negotiation scenario. Format is text using one of the listed labels. For example, \"discount_request\"."
    • changedInput schema / properties / value_delivered / description
      Previous value: -"Quantified value your solution delivers"New value: +"Quantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own. Format is text. For example, \"200 to 500 employees\"."
    • changedInput schema / properties / your_leverage / description
      Previous value: -"Your leverage points (unique features, timeline, etc.)"New value: +"Your leverage points (unique features, timeline, etc.). Format is text. For example, \"renewal decision depends on a documented approval process\"."
    • 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. Named in the guide and used, with your leverage, to read the sector and how you charge. Format is text. For example, \"invoice review service\"."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, and the description still adds real context: no sign-in, no storage of inputs or outputs, hosted usage metadata recorded, and errors that name the missing or invalid field. It does not cover latency, rate limits, or how large an input payload can be, so it stops short of full behavioral disclosure.

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 purpose and the input/output contract, then the routing rule and privacy notes. It is slightly longer than needed — the input enumeration partially repeats schema fields — but no sentence is pure filler and the ordering is logical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no output schema, the description covers inputs, the shape of the returned guidance, privacy/auth posture, and error behavior, which is close to complete. Minor gaps remain, such as whether optional fields change output quality and how unconfirmed authority alters the returned strategy beyond 'holds commitment to terms'.

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 baseline is 3, but the description adds meaning beyond the schema by grouping inputs (scenario, deal value, discount asked, each side's leverage, who approves) and by stating that value_delivered is used word for word and the guide adds no value figure of its own. It also frames pricing_authority_status as a confirmed fact rather than a role title, which changes how the agent should fill it.

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 answer a discount request without giving away margin, then enumerates what it returns (leverage assessment, value-based strategy, pushback answers, discount approval framework). It explicitly distinguishes itself from roi_business_case_builder, so an agent can route correctly 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit alternative and the selecting condition: use this instead of roi_business_case_builder when you need responses and approval guidance for a discount discussion. It also adds an in-conversation instruction (ask whether the user has authority to approve the proposed terms), which is actionable pre-call guidance.

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