Skip to main content
Glama
closermethod

SMB Sales Intelligence MCP

get_call_script

Retrieve structured call scripts for discovery or cold calls, providing key questions and conversation frameworks to guide sales conversations.

Instructions

Get a call script for discovery calls or cold calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_typeYesThe type of call script needed

Implementation Reference

  • Handler for the 'get_call_script' tool. Extracts call_type from args, looks it up in CALL_SCRIPTS, and returns the result.
    case "get_call_script": {
      const callType = args?.call_type as string;
      const script = CALL_SCRIPTS[callType as keyof typeof CALL_SCRIPTS];
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            module: "Call Scripts",
            ...script
          }, null, 2)
        }]
      };
    }
  • Registration of the 'get_call_script' tool with its name, description, and inputSchema (requires 'call_type' enum: discovery_call, cold_call).
    {
      name: "get_call_script",
      description: "Get a call script for discovery calls or cold calls.",
      inputSchema: {
        type: "object",
        properties: {
          call_type: {
            type: "string",
            enum: ["discovery_call", "cold_call"],
            description: "The type of call script needed"
          }
        },
        required: ["call_type"]
      }
  • The CALL_SCRIPTS constant containing discovery_call and cold_call script data.
    const CALL_SCRIPTS = {
      discovery_call: {
        name: "Discovery Call Framework",
        duration: "30 minutes",
        structure: {
          opening: {
            time: "2 min",
            script: "Thanks for taking the time. Before we dive in, I want to set expectations — my goal today is to understand what you're working on and see if there's a fit. If there is, great. If not, totally fine — I'll point you in the right direction. Sound good?"
          },
          their_situation: {
            time: "10 min",
            questions: [
              "Tell me about what's happening right now with [topic]. What prompted you to take this call?",
              "What have you tried so far? What worked, what didn't?",
              "If you solved this, what would that mean for [company/team/you personally]?",
              "What happens if you don't solve this?"
            ]
          },
          your_solution: {
            time: "10 min",
            script: "Based on what you've shared, here's how I typically help companies in your situation... [Explain your approach, not your product features]"
          },
          next_steps: {
            time: "5 min",
            script: "So here's what I'm thinking for next steps. I'll put together 3 options based on what we discussed and send them over by [date]. You review, and if one of them makes sense, we can move forward. If not, no pressure. Does that work?"
          },
          closing: {
            time: "3 min",
            script: "Before we wrap — is there anything else I should know? Anyone else who needs to be involved? Any timeline I should be aware of?"
          }
        }
      },
      cold_call: {
        name: "Cold Call Framework",
        duration: "2-3 minutes max",
        structure: {
          permission: {
            script: "Hi [Name], this is [Your name] from [Company]. Did I catch you at a bad time?"
          },
          reason: {
            script: "I'll be quick — I'm reaching out because I noticed [observation about their company]. I help similar companies with [outcome]. Is that something you're working on right now?"
          },
          if_yes: {
            script: "Great — can I ask what's driving that? What's the main challenge you're running into?"
          },
          if_no: {
            script: "No worries. Is this 'not right now' or 'not ever'? If it's timing, I'm happy to reach out later."
          },
          book_meeting: {
            script: "Sounds like there might be a fit. How's [specific date/time] for a 20-minute call to dig deeper?"
          }
        },
        rules: [
          "Keep it under 3 minutes",
          "Don't pitch — just qualify",
          "If they're busy, ask for a better time — don't launch into your script",
          "Sound like a person, not a robot reading a script"
        ]
      }
    };
  • src/main.ts:659-796 (registration)
    The ListToolsRequestSchema handler where 'get_call_script' is registered as one of the available tools (line 762-775).
    // Register available tools
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "get_discovery_script",
            description: "Get a discovery script to qualify prospects before pitching. Always ask questions first.",
            inputSchema: {
              type: "object",
              properties: {
                tone: {
                  type: "string",
                  enum: ["professional", "warm", "ultra_short", "cold_outbound", "inbound_lead"],
                  description: "professional=email/linkedin, warm=existing relationship, ultra_short=DM, cold_outbound=first contact, inbound_lead=they reached out"
                }
              },
              required: ["tone"]
            }
          },
          {
            name: "get_objection_response",
            description: "Handle a specific sales objection with psychology-backed responses.",
            inputSchema: {
              type: "object",
              properties: {
                objection_type: {
                  type: "string",
                  enum: ["too_expensive", "no_budget", "need_approval", "comparing_options", "bad_timing", "already_have_someone", "send_info", "need_to_think", "too_soon", "ghosting"],
                  description: "The type of objection to handle"
                }
              },
              required: ["objection_type"]
            }
          },
          {
            name: "get_followup_sequence",
            description: "Get a follow-up sequence for different situations (post-proposal, post-call, cold outbound, revival).",
            inputSchema: {
              type: "object",
              properties: {
                sequence_type: {
                  type: "string",
                  enum: ["post_proposal", "post_call", "cold_outbound", "revival"],
                  description: "The type of follow-up sequence needed"
                }
              },
              required: ["sequence_type"]
            }
          },
          {
            name: "get_closing_script",
            description: "Get a closing script based on the situation.",
            inputSchema: {
              type: "object",
              properties: {
                style: {
                  type: "string",
                  enum: ["standard", "assumptive", "timeline", "scarcity", "retainer", "choice", "next_step"],
                  description: "The closing style to use"
                }
              },
              required: ["style"]
            }
          },
          {
            name: "get_pricing_framework",
            description: "Get the 3-option pricing framework and templates.",
            inputSchema: {
              type: "object",
              properties: {},
              required: []
            }
          },
          {
            name: "get_emea_intelligence",
            description: "Get market intelligence for selling to a specific European country.",
            inputSchema: {
              type: "object",
              properties: {
                country: {
                  type: "string",
                  enum: ["uk", "ireland", "spain", "germany", "france", "netherlands", "nordics"],
                  description: "The EMEA market to get intelligence for"
                }
              },
              required: ["country"]
            }
          },
          {
            name: "get_cold_email_template",
            description: "Get a cold email template for outbound.",
            inputSchema: {
              type: "object",
              properties: {
                template_type: {
                  type: "string",
                  enum: ["pattern_interrupt", "observation", "mutual_connection", "case_study", "breakup"],
                  description: "The type of cold email template"
                }
              },
              required: ["template_type"]
            }
          },
          {
            name: "get_call_script",
            description: "Get a call script for discovery calls or cold calls.",
            inputSchema: {
              type: "object",
              properties: {
                call_type: {
                  type: "string",
                  enum: ["discovery_call", "cold_call"],
                  description: "The type of call script needed"
                }
              },
              required: ["call_type"]
            }
          },
          {
            name: "get_buying_signals",
            description: "Get a list of buying signals to watch for during sales conversations.",
            inputSchema: {
              type: "object",
              properties: {},
              required: []
            }
          },
          {
            name: "get_full_playbook",
            description: "Get the complete sales playbook with all modules.",
            inputSchema: {
              type: "object",
              properties: {},
              required: []
            }
          }
        ]
      };
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, required permissions, or what the output format is. This leaves the agent with minimal behavioral context.

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

Conciseness4/5

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

The description is a single sentence with no extraneous information. It is appropriately sized for the tool's simplicity, though it could be more structured with additional context. No wasted content.

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

Completeness2/5

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

The description lacks information about the output (e.g., format, structure). Given the absence of an output schema, the description should clarify what the agent can expect to receive. It also does not explain how 'call script' is defined, leaving ambiguity.

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?

The input schema covers the single parameter 'call_type' with full description and enum values. The description does not add extra meaning beyond restating the enum options. Baseline score of 3 is appropriate given 100% schema coverage.

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

Purpose4/5

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

The description clearly states it retrieves a call script for discovery or cold calls. It specifies the resource and type, distinguishing it from unrelated tools, but does not explicitly differentiate from the sibling tool 'get_discovery_script' which may overlap.

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

Usage Guidelines3/5

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

The description implies usage when needing a script for discovery or cold calls, but provides no guidance on when to use this tool instead of siblings like 'get_discovery_script' or 'get_closing_script'. No exclusions or alternatives are mentioned.

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/closermethod/smb-sales-intelligence-mcp'

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