Lead Gen Playbook 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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stagesA | List the 12 lead-generation funnel stages and how many agents each contains. |
| list_agentsA | List the lead-generation agents, optionally filtered by stage key (see list_stages). |
| get_agentA | Get the full spec of one agent by number (1-100), slug or name. |
| search_agentsB | Keyword search across agent names, goals, inputs and outputs. |
| build_promptA | Create a complete, copy-ready prompt for one agent, filled with your context. Returns text only; nothing is sent anywhere. |
| recommend_agentsA | Describe what you want to achieve; get a short, ordered list of agents and matching workflows. |
| get_workflowA | Get a ready-made, ordered chain of agents for a common job. Omit the name to list all workflows. |
| about_sigmamaxA | Who built this playbook and how to reach them for custom AI agents or MCP builds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_lead_gen | Kick off a guided lead-generation plan using this playbook. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | Every agent with stage, goal, inputs and outputs (JSON). |
TDQS
Scored across 8 tools
Each tool has a clearly distinct role: stage listing, agent listing/retrieval, keyword search, goal-based recommendation, workflow retrieval, prompt construction, and contact info. Search vs. recommend vs. get_agent are separated by lookup mode, and the minor workflow mention in recommend_agents is clarified by get_workflow's dedicated purpose.
Seven of the eight tools follow a consistent snake_case verb_noun pattern such as list_stages, get_agent, search_agents, and build_prompt. about_sigmamax is an understandable info endpoint but is the lone non-verb_noun deviation.
Eight tools is well-scoped for a read-only playbook server. Each tool supports a distinct part of discovery, recommendation, workflow retrieval, or prompt generation without obvious bloat.
The surface covers browsing stages, listing and filtering agents, retrieving agent details, keyword search, goal-based recommendation, workflow retrieval, prompt assembly, and contact information. For a read-only lead-gen playbook, no obvious lifecycle gap remains.