Outbound Engine 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 |
|---|---|
| structure_cold_pitchA | Get the HOOK / BRIDGE / SOFT ASK structure plus the 4 swap variables (who to pitch, signal to research, proof to lead with, soft-ask object) for a target type. Target types: brand_deal, ugc, newsletter_sponsorship, job, podcast, client_work. |
| audit_cold_messageA | Audit a drafted cold message against the engine rules: no money/rates, no identity-first opener, specific hook required, soft ask only, under ~90 words, one ask. Returns PASS/FAIL with named violations and a rewrite recipe. |
| build_followup_ladderA | Returns the 5-step follow-up ladder (Day 3 bump, Day 7 value-give, Day 12 new proof, Day 18 soft close, Day 25 break-up) with the move and rule for each rung. 80% of deals close in follow-up; the break-up alone pulls ~30% of replies. |
| handle_replyA | Given the type of reply received, returns what it means, the next move, the reply shape, and the trap to avoid. Reply types: price_question, interested, not_now, no_budget, exposure_offer, spec_request, pay_on_performance, ghosted_after_interest. |
| build_pricing_menuA | Returns the 3-option menu structure (Starter / Most Popular / Full), the two scoping questions to ask FIRST for the target type, and the drop-scope-not-price negotiation rule. Use only after the prospect asks about price — never in a cold message. |
| detect_red_flagsA | Scan a prospect's reply or brief for walk-away signals: exposure-pay, spec-work requests, pay-on-performance, budget mismatch, scope-creep probes. Returns flags found and a CLEAN/CAUTION/WALK verdict. |
| get_full_packA | Returns the complete engine: core rules, all target packs, follow-up ladder, reply playbook, pricing menu, red flags. Useful for full agent context (e.g. a Claude Project system prompt). |
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 7 tools
Each tool targets a distinct stage or aspect of the outbound workflow: pitch creation, pitch audit, reply interpretation, red-flag detection, pricing, follow-up, and full context. No two tools share the same purpose, even though some operate on similar inputs (replies or pitches).
All tool names follow a consistent verb_noun pattern in lowercase snake_case (handle_reply, build_pricing_menu, detect_red_flags, get_full_pack, structure_cold_pitch, audit_cold_message, build_followup_ladder). Verbs are clear and parallel.
Seven tools is well-scoped for an outbound engagement engine, covering the core stages without redundancy. The count is within the ideal range and each tool earns its place.
The tools cover the full lifecycle: structuring a pitch, auditing it, handling replies, detecting red flags, providing pricing guidance, building follow-up ladders, and retrieving the entire engine context. There are no obvious dead ends or missing operations for the server's stated purpose.