LeadClaw 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| book_appointmentsA | Request confirmed sales appointments delivered to your calendar. Human SDRs handle outbound; you pay only per confirmed, BANT-qualified meeting. Use when the user wants to book meetings, generate pipeline, get demos, or set up sales calls — but does not want to do the outreach themselves. Returns a request_id; poll check_status to see confirmed appointments populate. |
| check_statusA | Check the progress of a LeadClaw appointment request. Returns current phase (processing / matching / in_progress / completed) and any confirmed appointments so far. Call this after book_appointments and re-poll as needed until status is completed. |
| get_appointment_detailsA | Pull full briefing on a specific confirmed appointment: contact info, company context, full BANT breakdown, SDR call notes, and meeting link. Use when the user wants to prep for a specific meeting. |
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 3 tools
Each tool serves a distinct purpose: booking appointments, checking status, and retrieving details. There is no ambiguity between them.
All tools follow the verb_noun pattern with snake_case (book_appointments, check_status, get_appointment_details), providing a predictable naming scheme.
Three tools is slightly minimal for the domain but covers the core workflow of booking, tracking, and reviewing appointments. It is reasonable for the service's scope.
The tool set covers the primary lifecycle (book, monitor, view details). Minor gaps like cancellation or rescheduling exist but are not critical for the stated purpose.