Lead Leak Check
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_pipelineA | Check a structured lead-pipeline config and return a ranked leak-risk list. Keys (all optional; omitted ones are reported as 'verify'): name; sources: [{type: web_form|whatsapp|email|ads_lead_form|instagram_dm|..., required_contact_field: bool, logged_to_storage: bool}]; storage: {type: google_sheets|crm|airtable|none, dedupe: bool}; routing: {owner_assignment: round_robin|fixed|none, after_hours_coverage: bool}; response: {sla_minutes: int, auto_ack: bool, ai_drafts: bool, human_send_step: bool}; monitoring: {error_alerts: bool, unanswered_lead_alert: bool, run_history_review: weekly|never}; automation: {platform: zapier|make|n8n, plan: free|paid}; timezone: {business_tz, automation_tz}; follow_up: {sequence: bool} |
| check_pipeline_descriptionC | Check a plain-English description of how leads arrive, where they are stored, who replies and what alerts exist. |
| analyze_run_historyA | Analyze a run-history CSV (needs a status column; a timestamp column enables gap and stale checks). Flags failed/halted runs, filtered runs that end without errors, long gaps with no runs, and a stale last run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_rules | All leak rules with severity, explanation and fix. |
TDQS
Scored across 3 tools
The three tools target distinct input types: structured config, plain-English description, and run-history CSV. However, check_pipeline and check_pipeline_description have nearly identical names and purposes, which could cause misselection when the input format is ambiguous.
All tools use consistent snake_case verb_noun naming (check_pipeline, check_pipeline_description, analyze_run_history). The longer check_pipeline_description is still predictable within the same convention.
Three tools are well-scoped for a focused lead-leak diagnostic server. The count is slightly thin and two tools are input-format variants of the same check, but neither is excessive.
The surface covers structured pipeline checks, natural-language descriptions, and run-history analysis, which are the main diagnostic inputs. Minor gaps remain: no tool to consolidate findings or recommend fixes, and no direct lead-level audit.