Build our message for this segment
impact_build_segment_messageBuilds a segment-specific B2B message from a brief, flags proof gaps, maps champion and alternative choices, then returns the message and proof plan after buyer confirmation.
Instructions
Helps you decide how to build a message for one segment when sellers do not use it or buyers keep their current approach. Needs the product, segment, champion problem, alternatives, outcome, capability and proof. Returns proof gaps and current approach questions, champion and alternatives maps for human choices, then a message and proof plan after a pause. Optional agreed workshop claim is the starting point. Without a real customer result, buyer lines are unproved hypotheses and the next step is discovery questions. Chat carries the brief between calls. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing or invalid stage or brief fields return field-specific errors. The message stage requires the matching review receipt and confirmed choices. Missing real proof keeps buyer lines as unproved hypotheses. Use this instead of impact_craft_message when you need a staged segment workshop with confirmed champion and alternative choices.
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": {
"stage": "<stage>",
"brief": "<brief>"
},
"name": "impact_build_segment_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| brief | Yes | The segment brief carried unchanged between calls. Format is a JSON object. For example, {"product":"invoice review service","product_description":"checks invoice exceptions before approval","segments":["manufacturers with 200 to 500 employees"],"problem":"invoice exceptions delay month-end close","category":"manufacturing","alternatives":["the current manual review process"],"desired_outcome":"resolve invoice exceptions before month-end","capability":"checks invoice exceptions before approval","trigger":"an audit review due next quarter","measure":"days from invoice receipt to approval","sector":"manufacturing","proof":{"kind":"none"}}. | |
| stage | Yes | Map first. After the buyer chooses, call message with the same brief, its review receipt and confirmed choices. Format is text using one of the listed labels. For example, "map". | |
| choices | No | The champion and alternative choices confirmed by the buyer after reading the maps. Format is a JSON object. For example, {"confirmed":true,"champion":"finance director","champion_segment":"manufacturers with 200 to 500 employees","alternative":"the current manual review process"}. | |
| review_receipt | No | The receipt from the map call, carried by chat. The server stores no brief. Format is text. For example, "copy the complete receipt returned by the map call". |