Proposal Section Writer
proposal_section_writerDraft 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
| Name | Required | Description | Default |
|---|---|---|---|
| tone | No | Tone for the proposal (changes only the opening of the executive summary). Format is text using one of the listed labels. For example, "formal". | |
| pricing | No | Pricing details if relevant. Format is text. For example, "USD 24000 per year". | |
| your_sector | No | 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". | |
| section_type | Yes | Proposal section to generate. Format is text using one of the listed labels. For example, "executive_summary". | |
| customer_name | No | Customer name. Format is text. For example, "an approved anonymous manufacturer". | |
| your_solution | Yes | Your product/solution. Format is text. For example, "invoice review service". | |
| success_metrics | No | Expected outcomes/metrics. Format is text. For example, "median approval time measured monthly". | |
| primary_audience | No | 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". | |
| customer_industry | No | Customer industry. Format is text. For example, "manufacturing". | |
| customer_challenges | No | Key challenges identified. Format is text. For example, "invoice exceptions delay close". | |
| key_differentiators | No | Why you vs alternatives. Format is text. For example, "checks invoice exceptions before approval". | |
| implementation_approach | No | How you will implement. Format is text. For example, "pilot with one finance team before rollout". |