Skip to main content
Glama
enzoemir1

leadpipe-mcp

Score Lead

lead_score
Idempotent

Compute a six-dimensional lead score (0-100) weighted by configurable rules, then update lead status to qualified or disqualified based on a 60-point threshold.

Instructions

Compute a 6-dimensional qualification score (0-100) for a lead: job_title, company_size, industry, engagement, recency, and custom_rules. Each dimension is weighted via config_scoring; the final score is their weighted average. Updates the lead status to "qualified" (≥60) or "disqualified" (<60) and stores score_breakdown alongside the total. Returns the updated lead with the breakdown. Run lead_enrich first for the most accurate industry/size signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lead_idYesUUID of the lead to score

Implementation Reference

  • Main scoring function: validates lead ID, computes 6-dimensional weighted score (job_title, company_size, industry, engagement, recency, custom_rules), determines status as qualified (>=60) or disqualified (<60), stores score_breakdown, and returns the updated lead.
    export async function scoreLead(leadId: string, store?: Storage): Promise<Lead> {
      if (!RE_UUID.test(leadId)) throw new ValidationError(`Invalid lead ID format: ${leadId}`);
    
      const s = store ?? defaultStorage;
      const lead = await s.getLeadById(leadId);
      if (!lead) throw new NotFoundError('Lead', leadId);
    
      const config = await s.getScoringConfig();
    
      const titleResult = scoreJobTitle(lead.job_title, config);
      const sizeResult = scoreCompanySize(lead.company?.size, config);
      const industryResult = scoreIndustry(lead.company?.industry, config);
      const engagementResult = scoreEngagement(lead);
      const recencyResult = scoreRecency(lead);
      const customResult = evaluateCustomRules(lead, config.custom_rules);
    
      // Weighted average
      const total = Math.round(
        titleResult.score * config.job_title_weight +
        sizeResult.score * config.company_size_weight +
        industryResult.score * config.industry_weight +
        engagementResult.score * config.engagement_weight +
        recencyResult.score * config.recency_weight +
        customResult.score * config.custom_rules_weight
      );
    
      const breakdown: ScoreBreakdown = {
        total,
        job_title_score: titleResult.score,
        company_size_score: sizeResult.score,
        industry_score: industryResult.score,
        engagement_score: engagementResult.score,
        recency_score: recencyResult.score,
        custom_rules_score: customResult.score,
        details: [
          ...titleResult.details,
          ...sizeResult.details,
          ...industryResult.details,
          ...engagementResult.details,
          ...recencyResult.details,
          ...customResult.details,
        ],
      };
    
      const status = total >= 60 ? 'qualified' : 'disqualified';
    
      const updated = await s.updateLead(leadId, {
        score: total,
        score_breakdown: breakdown,
        status,
        scored_at: new Date().toISOString(),
      });
    
      return updated!;
    }
  • Scores job title dimension (0-100) using regex matching against C-level, VP, Manager, Senior, Junior roles, custom high-value titles, or defaults.
    function scoreJobTitle(title: string | undefined, config: ScoringConfig): { score: number; details: ScoringDetail[] } {
      if (!title) return { score: 20, details: [{ rule: 'job_title', points: 20, reason: 'No job title provided' }] };
    
      const lower = title.toLowerCase();
      const details: ScoringDetail[] = [];
    
      // C-level / Founder
      if (RE_CLEVEL.test(lower)) {
        details.push({ rule: 'job_title_clevel', points: 100, reason: `C-level/Founder: ${title}` });
        return { score: 100, details };
      }
    
      // VP / Director / Head
      if (RE_VP.test(lower)) {
        details.push({ rule: 'job_title_vp', points: 85, reason: `VP/Director level: ${title}` });
        return { score: 85, details };
      }
    
      // Manager
      if (RE_MANAGER.test(lower)) {
        details.push({ rule: 'job_title_manager', points: 65, reason: `Manager level: ${title}` });
        return { score: 65, details };
      }
    
      // Check against custom high-value titles
      const isHighValue = config.high_value_titles.some((t) => lower.includes(t.toLowerCase()));
      if (isHighValue) {
        details.push({ rule: 'job_title_custom', points: 70, reason: `Matches high-value title: ${title}` });
        return { score: 70, details };
      }
    
      // Senior
      if (RE_SENIOR.test(lower)) {
        details.push({ rule: 'job_title_senior', points: 50, reason: `Senior role: ${title}` });
        return { score: 50, details };
      }
    
      // Junior / Intern / Student
      if (RE_JUNIOR.test(lower)) {
        details.push({ rule: 'job_title_junior', points: 15, reason: `Junior role: ${title}` });
        return { score: 15, details };
      }
    
      details.push({ rule: 'job_title_other', points: 35, reason: `Standard role: ${title}` });
      return { score: 35, details };
    }
  • Scores company size dimension (0-100) - preferred sizes get 90, others mapped via sizeScores lookup.
    function scoreCompanySize(size: string | undefined, config: ScoringConfig): { score: number; details: ScoringDetail[] } {
      if (!size) return { score: 30, details: [{ rule: 'company_size', points: 30, reason: 'Company size unknown' }] };
    
      const isPreferred = config.preferred_company_sizes.includes(size as any);
      if (isPreferred) {
        return { score: 90, details: [{ rule: 'company_size_preferred', points: 90, reason: `Preferred size: ${size}` }] };
      }
    
      const sizeScores: Record<string, number> = {
        '1-10': 40,
        '11-50': 70,
        '51-200': 85,
        '201-500': 80,
        '501-1000': 65,
        '1001-5000': 55,
        '5000+': 45,
      };
    
      const score = sizeScores[size] ?? 30;
      return { score, details: [{ rule: 'company_size', points: score, reason: `Company size: ${size}` }] };
    }
  • Scores industry dimension (0-100) - high-value industries get 90, standard ones get 40.
    function scoreIndustry(industry: string | undefined, config: ScoringConfig): { score: number; details: ScoringDetail[] } {
      if (!industry) return { score: 30, details: [{ rule: 'industry', points: 30, reason: 'Industry unknown' }] };
    
      const lower = industry.toLowerCase();
      const isHighValue = config.high_value_industries.some((i) => lower.includes(i.toLowerCase()));
    
      if (isHighValue) {
        return { score: 90, details: [{ rule: 'industry_high_value', points: 90, reason: `High-value industry: ${industry}` }] };
      }
    
      return { score: 40, details: [{ rule: 'industry_standard', points: 40, reason: `Standard industry: ${industry}` }] };
    }
  • Scores engagement dimension (0-100 capped) based on phone, full name, tags, custom fields, and source signals.
    function scoreEngagement(lead: Lead): { score: number; details: ScoringDetail[] } {
      let score = 30; // baseline
      const details: ScoringDetail[] = [];
    
      // Has phone number (engagement signal)
      if (lead.phone) {
        score += 15;
        details.push({ rule: 'engagement_phone', points: 15, reason: 'Phone number provided' });
      }
    
      // Has full name
      if (lead.first_name && lead.last_name) {
        score += 10;
        details.push({ rule: 'engagement_fullname', points: 10, reason: 'Full name provided' });
      }
    
      // Has tags (shows interaction/categorization)
      if (lead.tags.length > 0) {
        score += 10;
        details.push({ rule: 'engagement_tags', points: 10, reason: `Has ${lead.tags.length} tags` });
      }
    
      // Has custom fields
      if (Object.keys(lead.custom_fields).length > 0) {
        score += 10;
        details.push({ rule: 'engagement_custom', points: 10, reason: 'Has custom fields' });
      }
    
      // Source signals
      const sourceScores: Record<string, number> = {
        website_form: 15,
        landing_page: 20,
        webhook: 10,
        api: 5,
        manual: 10,
        csv_import: 0,
      };
      const sourceBonus = sourceScores[lead.source] ?? 0;
      if (sourceBonus > 0) {
        score += sourceBonus;
        details.push({ rule: 'engagement_source', points: sourceBonus, reason: `Source: ${lead.source}` });
      }
    
      return { score: Math.min(score, 100), details };
    }
  • Scores recency dimension (0-100) based on days since lead creation.
    function scoreRecency(lead: Lead): { score: number; details: ScoringDetail[] } {
      const now = Date.now();
      const created = new Date(lead.created_at).getTime();
      const daysSince = (now - created) / (1000 * 60 * 60 * 24);
    
      let score: number;
      let reason: string;
    
      if (daysSince <= 1) {
        score = 100;
        reason = 'Created today';
      } else if (daysSince <= 3) {
        score = 90;
        reason = 'Created in last 3 days';
      } else if (daysSince <= 7) {
        score = 75;
        reason = 'Created in last week';
      } else if (daysSince <= 14) {
        score = 55;
        reason = 'Created in last 2 weeks';
      } else if (daysSince <= 30) {
        score = 35;
        reason = 'Created in last month';
      } else if (daysSince <= 90) {
        score = 15;
        reason = 'Created 1-3 months ago';
      } else {
        score = 5;
        reason = 'Created over 3 months ago';
      }
    
      return { score, details: [{ rule: 'recency', points: score, reason }] };
    }
  • Evaluates custom rules against lead fields with operators (equals, contains, starts_with, ends_with, gt, lt, regex) and normalizes to 0-100.
    function evaluateCustomRules(lead: Lead, rules: CustomRule[]): { score: number; details: ScoringDetail[] } {
      if (rules.length === 0) return { score: 50, details: [{ rule: 'custom_rules', points: 50, reason: 'No custom rules configured' }] };
    
      let totalPoints = 0;
      const details: ScoringDetail[] = [];
    
      for (const rule of rules) {
        const fieldValue = getFieldValue(lead, rule.field);
        if (fieldValue === undefined) continue;
    
        const matches = evaluateCondition(String(fieldValue), rule.operator, rule.value);
        if (matches) {
          totalPoints += rule.points;
          details.push({
            rule: `custom_${rule.field}`,
            points: rule.points,
            reason: rule.description,
          });
        }
      }
    
      // Normalize to 0-100
      const score = Math.max(0, Math.min(100, 50 + totalPoints));
      return { score, details };
    }
  • ScoreBreakdownSchema defining the 6-dimensional score structure plus total and details array.
    /** Breakdown of a lead's score across all dimensions. */
    export const ScoreBreakdownSchema = z.object({
      total: z.number().min(0).max(100),
      job_title_score: z.number().min(0).max(100),
      company_size_score: z.number().min(0).max(100),
      industry_score: z.number().min(0).max(100),
      engagement_score: z.number().min(0).max(100),
      recency_score: z.number().min(0).max(100),
      custom_rules_score: z.number().min(0).max(100),
      details: z.array(ScoringDetailSchema),
    });
    export type ScoreBreakdown = z.infer<typeof ScoreBreakdownSchema>;
  • ScoringConfigSchema: weights (job_title, company_size, industry, engagement, recency, custom_rules), high_value_titles/industries, preferred_company_sizes, and custom_rules defaults.
    export const ScoringConfigSchema = z.object({
      job_title_weight: z.number().min(0).max(1).default(0.25),
      company_size_weight: z.number().min(0).max(1).default(0.20),
      industry_weight: z.number().min(0).max(1).default(0.20),
      engagement_weight: z.number().min(0).max(1).default(0.15),
      recency_weight: z.number().min(0).max(1).default(0.10),
      custom_rules_weight: z.number().min(0).max(1).default(0.10),
      high_value_titles: z
        .array(z.string())
        .default(['ceo', 'cto', 'vp', 'director', 'head', 'founder', 'owner', 'manager']),
      high_value_industries: z
        .array(z.string())
        .default(['saas', 'technology', 'software', 'fintech', 'ecommerce', 'marketing', 'consulting']),
      preferred_company_sizes: z.array(CompanySizeSchema).default(['11-50', '51-200', '201-500']),
      custom_rules: z.array(CustomRuleSchema).default([]),
    });
    export type ScoringConfig = z.infer<typeof ScoringConfigSchema>;
  • CustomRuleSchema: field, operator, value, points (-50 to +50), and description for custom scoring rules.
    export const CustomRuleSchema = z.object({
      field: z.string().describe('Lead field to evaluate. Dot-paths are supported (e.g. "email", "job_title", "company.industry", "custom_fields.utm_source").'),
      operator: OperatorSchema.describe('How field is compared to value: "equals" / "contains" / "starts_with" / "ends_with" for strings, "gt" / "lt" for numeric, or "regex" for full pattern match.'),
      value: z.string().describe('Comparison value as a string. For numeric operators (gt/lt) the string is parsed as a number. For regex it is the pattern.'),
      points: z.number().min(-50).max(50).describe('Score adjustment when the rule matches. Range -50..+50. Positive boosts the lead, negative penalizes.'),
      description: z.string().describe('Human-readable description shown in score_breakdown.details so users understand why a lead got the points.'),
    });
    export type CustomRule = z.infer<typeof CustomRuleSchema>;
  • ScoringDetailSchema for individual rule results with rule name, points, and reason.
    /** Details of a single scoring rule application. */
    export const ScoringDetailSchema = z.object({
      rule: z.string(),
      points: z.number(),
      reason: z.string(),
    });
    export type ScoringDetail = z.infer<typeof ScoringDetailSchema>;
  • src/index.ts:211-250 (registration)
    Tool registration (lead_score) on the MCP server with inputSchema (lead_id UUID) and handler that calls scoreLead.
    // ━━━ TOOL: lead_score ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    server.registerTool(
      'lead_score',
      {
        title: 'Score Lead',
        description:
          'Compute a 6-dimensional qualification score (0-100) for a lead: job_title, company_size, industry, engagement, recency, and custom_rules. Each dimension is weighted via config_scoring; the final score is their weighted average. Updates the lead status to "qualified" (≥60) or "disqualified" (<60) and stores score_breakdown alongside the total. Returns the updated lead with the breakdown. Run lead_enrich first for the most accurate industry/size signals.',
        inputSchema: z.object({
          lead_id: z.string().uuid().describe('UUID of the lead to score'),
        }),
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      },
      async ({ lead_id }) => {
        try {
          const lead = await scoreLead(lead_id);
          const breakdown = lead.score_breakdown;
          return {
            content: [
              {
                type: 'text' as const,
                text: [
                  `Lead scored: ${lead.email} → ${lead.score}/100 (${lead.status})`,
                  '',
                  'Breakdown:',
                  `  Job Title: ${breakdown?.job_title_score}/100`,
                  `  Company Size: ${breakdown?.company_size_score}/100`,
                  `  Industry: ${breakdown?.industry_score}/100`,
                  `  Engagement: ${breakdown?.engagement_score}/100`,
                  `  Recency: ${breakdown?.recency_score}/100`,
                  `  Custom Rules: ${breakdown?.custom_rules_score}/100`,
                ].join('\n'),
              },
            ],
            structuredContent: lead,
          };
        } catch (error) {
          return handleToolError(error);
        }
      }
    );
  • Pre-compiled regex patterns for job title scoring: C-level, VP, Manager, Senior, Junior.
    const RE_JUNIOR = /\b(junior|jr\.?|intern|student|trainee|assistant)\b/;
    const RE_UUID = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
    
    // Max regex pattern length to prevent ReDoS attacks
    const MAX_REGEX_LENGTH = 200;
    
    function scoreJobTitle(title: string | undefined, config: ScoringConfig): { score: number; details: ScoringDetail[] } {
      if (!title) return { score: 20, details: [{ rule: 'job_title', points: 20, reason: 'No job title provided' }] };
    
      const lower = title.toLowerCase();
      const details: ScoringDetail[] = [];
    
      // C-level / Founder
      if (RE_CLEVEL.test(lower)) {
        details.push({ rule: 'job_title_clevel', points: 100, reason: `C-level/Founder: ${title}` });
        return { score: 100, details };
      }
    
      // VP / Director / Head
      if (RE_VP.test(lower)) {
        details.push({ rule: 'job_title_vp', points: 85, reason: `VP/Director level: ${title}` });
        return { score: 85, details };
      }
    
      // Manager
      if (RE_MANAGER.test(lower)) {
        details.push({ rule: 'job_title_manager', points: 65, reason: `Manager level: ${title}` });
        return { score: 65, details };
      }
    
      // Check against custom high-value titles
      const isHighValue = config.high_value_titles.some((t) => lower.includes(t.toLowerCase()));
      if (isHighValue) {
        details.push({ rule: 'job_title_custom', points: 70, reason: `Matches high-value title: ${title}` });
        return { score: 70, details };
      }
    
      // Senior
      if (RE_SENIOR.test(lower)) {
        details.push({ rule: 'job_title_senior', points: 50, reason: `Senior role: ${title}` });
        return { score: 50, details };
  • getFieldValue helper to extract lead field values (including dot-paths like company.name).
    function getFieldValue(lead: Lead, field: string): string | undefined {
      const map: Record<string, string | undefined> = {
        email: lead.email,
        first_name: lead.first_name,
        last_name: lead.last_name,
        full_name: lead.full_name,
        job_title: lead.job_title,
        phone: lead.phone,
        source: lead.source,
        company_name: lead.company?.name,
        company_domain: lead.company?.domain,
        company_industry: lead.company?.industry,
        company_size: lead.company?.size,
        company_country: lead.company?.country,
      };
    
      // Check custom_fields as fallback
      return map[field] ?? lead.custom_fields[field];
    }
  • evaluateCondition helper implementing string/numeric/regex operators for custom rules.
    function evaluateCondition(value: string, operator: string, target: string): boolean {
      if (!value || !target) return false;
    
      const lower = value.toLowerCase();
      const targetLower = target.toLowerCase();
    
      switch (operator) {
        case 'equals': return lower === targetLower;
        case 'contains': return lower.includes(targetLower);
        case 'starts_with': return lower.startsWith(targetLower);
        case 'ends_with': return lower.endsWith(targetLower);
        case 'gt': {
          const a = parseFloat(value);
          const b = parseFloat(target);
          return Number.isFinite(a) && Number.isFinite(b) && a > b;
        }
        case 'lt': {
          const a = parseFloat(value);
          const b = parseFloat(target);
          return Number.isFinite(a) && Number.isFinite(b) && a < b;
        }
        case 'regex': {
          // ReDoS protection: limit pattern length and reject dangerous patterns
          if (target.length > MAX_REGEX_LENGTH) return false;
          try {
            const re = new RegExp(target, 'i');
            return re.test(value);
          } catch {
            return false;
          }
        }
        default: return false;
      }
    }
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description confirms mutation (lead status update) and idempotency (weighted average of dimensions), adding details beyond annotations (thresholds, breakdown storage). No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences concisely cover dimensions, weighting, status update, return value, and prerequisite. No redundant words; information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given tool complexity (6 dimensions, weighted scoring, status mutation, prerequisite), description covers all essential aspects. No output schema, but return value is described as updated lead with breakdown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has full coverage (100%) with detailed description of lead_id (UUID format). Description adds no param-specific info beyond schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool computes a 6-dimensional qualification score, updates lead status, and stores breakdown, with specific verb 'compute' and resource 'lead'. It distinguishes from siblings like lead_enrich and lead_qualify by detailing the multi-dimensional scoring and status update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises to 'Run lead_enrich first for the most accurate industry/size signals', providing a clear precondition. While it doesn't explicitly state when not to use, the context and singleton parameter make usage straightforward.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/enzoemir1/leadpipe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server