Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Proposal Section Writer

proposal_section_writer
Read-only

Draft one seller-authored proposal section from your solution, buyer challenges, differentiators, pricing, and success metrics; get sector notes and no invented facts.

Instructions

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.

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": {
      "section_type": "<section_type>",
      "your_solution": "<your_solution>"
    },
    "name": "proposal_section_writer"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoTone for the proposal (changes only the opening of the executive summary). Format is text using one of the listed labels. For example, "formal".
pricingNoPricing details if relevant. Format is text. For example, "USD 24000 per year".
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".
section_typeYesProposal section to generate. Format is text using one of the listed labels. For example, "executive_summary".
customer_nameNoCustomer name. Format is text. For example, "an approved anonymous manufacturer".
your_solutionYesYour product/solution. Format is text. For example, "invoice review service".
success_metricsNoExpected outcomes/metrics. Format is text. For example, "median approval time measured monthly".
primary_audienceNoAdds a one-line note at the top of the executive summary on what this audience looks for. Format is text using one of the listed labels. For example, "c_suite".
customer_industryNoCustomer industry. Format is text. For example, "manufacturing".
customer_challengesNoKey challenges identified. Format is text. For example, "invoice exceptions delay close".
key_differentiatorsNoWhy you vs alternatives. Format is text. For example, "checks invoice exceptions before approval".
implementation_approachNoHow you will implement. Format is text. For example, "pilot with one finance team before rollout".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.2.33
    • changedInput schema / properties / customer_challenges / description
      Previous value: -"Key challenges identified"New value: +"Key challenges identified. Format is text. For example, \"invoice exceptions delay close\"."
    • changedInput schema / properties / customer_industry / description
      Previous value: -"Customer industry"New value: +"Customer industry. Format is text. For example, \"manufacturing\"."
    • changedInput schema / properties / customer_name / description
      Previous value: -"Customer name"New value: +"Customer name. Format is text. For example, \"an approved anonymous manufacturer\"."
    • changedInput schema / properties / implementation_approach / description
      Previous value: -"How you will implement"New value: +"How you will implement. Format is text. For example, \"pilot with one finance team before rollout\"."
    • changedInput schema / properties / key_differentiators / description
      Previous value: -"Why you vs alternatives"New value: +"Why you vs alternatives. Format is text. For example, \"checks invoice exceptions before approval\"."
    • changedInput schema / properties / pricing / description
      Previous value: -"Pricing details if relevant"New value: +"Pricing details if relevant. Format is text. For example, \"USD 24000 per year\"."
    • changedInput schema / properties / primary_audience / description
      Previous value: -"Primary reader of proposal"New value: +"Adds a one-line note at the top of the executive summary on what this audience looks for. Format is text using one of the listed labels. For example, \"c_suite\"."
    • changedInput schema / properties / section_type / description
      Previous value: -"Proposal section to generate"New value: +"Proposal section to generate. Format is text using one of the listed labels. For example, \"executive_summary\"."
    • changedInput schema / properties / success_metrics / description
      Previous value: -"Expected outcomes/metrics"New value: +"Expected outcomes/metrics. Format is text. For example, \"median approval time measured monthly\"."
    • changedInput schema / properties / tone / description
      Previous value: -"Tone for the proposal"New value: +"Tone for the proposal (changes only the opening of the executive summary). Format is text using one of the listed labels. For example, \"formal\"."
    • 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\"."
  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 annotations, it discloses no-fabrication behavior ('invents no figure, customer or date'), that it reports missing inputs once, that no sign-in is needed and no inputs/outputs are stored, that hosted usage metadata is recorded, and that validation errors name the field to supply or correct. These are exactly the behavioral traits annotations cannot express.

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 purpose and output, then behavior, then a routing rule — a sensible order. A few clauses are dense or marginally redundant (such as 'Read-only for business data' alongside the readOnlyHint annotation), but no sentence is wasted.

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?

With 12 parameters (only 2 required), no output schema, and no nested objects, the description covers what it takes in, what it returns ('that section in sentences... with sector notes'), its privacy/hallucination guarantees, and its error behavior. Nothing an agent needs in order to call it correctly is missing.

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?

The description names the input categories (section, solution, challenges, differentiators, pricing, success measures), which maps onto several of the 12 parameters. However, schema description coverage is 100% and the schema already documents enum semantics (tone changes only the opening; your_sector drives sector notes; primary_audience adds a one-line note), so the description adds little meaning beyond structured data. Baseline 3 applies.

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 specific verb and output ('decide what to write', 'You get that section in sentences built from your inputs') plus the resource scope: exactly one proposal section for a buyer. It enumerates section types and explicitly distinguishes itself from champion_enablement_kit, so an agent can tell the two apart without opening either 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 condition that selects it: 'Use this instead of champion_enablement_kit when you need one seller-authored proposal section for the buyer.' Combined with the enumerated section types, the agent knows both when this tool applies and what to reach for otherwise.

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