Skip to main content
Glama
mambalabsdev

Prospect Engine MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_prospect_engineA

A composed prospecting actor with four modes. enrich_companies resolves identity, firmographics, LinkedIn and social for each domain or company name you supply, and needs no vendor key at all. discover_jobs finds who is hiring for your keywords and resolves the real employer behind each posting, including postings a job board placed on an employer's behalf. find_contacts finds people at the companies you name, with optional email discovery and verification. full runs discovery, enrichment, ICP scoring and then contact discovery, passing only the companies at or above min_icp_score through to the contact stage. Every row comes back flat and Clay ready with per field provenance. Vendor keys are yours: you supply them, those vendors bill you directly, and the per event price covers the actor only. discover_jobs and full require a SerpApi key, which is a different vendor from the Serper key that powers people search. Note that this actor is a pass through wrapper over the live actor, so any classification behavior you see is the actor's own. Requires an APIFY_TOKEN and consumes Apify credits. Read only: it enriches and discovers, it writes nothing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with others. The tool's name clearly indicates a single entry point, even though it internally supports multiple modes.

Naming Consistency5/5

The single tool name follows a clear 'verb_noun' pattern (run_prospect_engine), and there are no other tools to create inconsistency.

Tool Count2/5

Having only one tool for a multi-step prospecting workflow (enrichment, job discovery, contact finding) is under-scoped. The distinct functions would typically be separated into multiple tools for clarity and modularity.

Completeness4/5

Despite being a single tool, it covers the core prospecting actions described: enrichment, job discovery, ICP scoring, and contact discovery. As a read-only actor, no write operations are expected, so there are no obvious gaps in the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues