Skip to main content
Glama
akhilkannur

Salestools Club

by akhilkannur

get_starter_prompt

Retrieve a copy-paste starter prompt for any sales tool to use immediately with your AI agent. Simply provide the tool's slug to get started.

Instructions

Get the copy-paste starter prompt for a tool so you can immediately use it with your AI agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe tool's slug (e.g., 'hubspot', 'apollo', 'lusha')

Implementation Reference

  • The main handler function for the 'get_starter_prompt' tool. Fetches tool details by slug from the Salestools API, formats a starter prompt with AI capabilities and docs links.
    async function handleGetStarterPrompt(args) {
      const { slug } = args;
      try {
        const tool = await fetchJSON(`${BASE_URL}/api/tools/${encodeURIComponent(slug)}`);
        if (tool.error) {
          return { content: [{ type: "text", text: `Tool "${slug}" not found.` }] };
        }
    
        let text = `# ${tool.name} — Starter Prompt\n\n`;
    
        if (tool.starterPrompt) {
          text += `Copy this into Claude Code or any AI agent:\n\n`;
          text += `\`\`\`\n${tool.starterPrompt}\n\`\`\`\n\n`;
        } else {
          text += `No starter prompt available for ${tool.name} yet.\n\n`;
        }
    
        if (tool.aiCapabilities?.length > 0) {
          text += `## What you can ask your AI to do:\n`;
          text += tool.aiCapabilities.map(c => `- ${c}`).join('\n') + '\n\n';
        }
    
        if (tool.docsUrl) text += `API Docs: ${tool.docsUrl}\n`;
        if (tool.integrations?.length > 0) {
          const mcp = tool.integrations.find(i => i.platform === 'MCP');
          if (mcp) text += `MCP Server: ${mcp.url}\n`;
        }
    
        return { content: [{ type: "text", text: text.trim() }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Failed to fetch tool "${slug}": ${error.message}` }] };
      }
    }
  • Input schema registration for 'get_starter_prompt' tool. Defines the 'slug' parameter (required string) and the tool description.
    {
      name: "get_starter_prompt",
      description: "Get the copy-paste starter prompt for a tool so you can immediately use it with your AI agent.",
      inputSchema: {
        type: "object",
        properties: {
          slug: { type: "string", description: "The tool's slug (e.g., 'hubspot', 'apollo', 'lusha')" },
        },
        required: ["slug"],
      },
    },
  • index.js:312-312 (registration)
    Registration of 'get_starter_prompt' in the CallToolRequestSchema switch/case handler, routing to handleGetStarterPrompt.
    case "get_starter_prompt": return handleGetStarterPrompt(args);
  • Helper utility fetchJSON used by handleGetStarterPrompt to call the Salestools API with a 10-second timeout.
    async function fetchJSON(url) {
      const response = await fetch(url, { signal: AbortSignal.timeout(10000) });
      if (!response.ok) throw new Error(`API error: ${response.status} ${response.statusText}`);
      return response.json();
    }
Behavior2/5

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

No annotations provided, and description only says 'copy-paste starter prompt', failing to disclose any potential side effects, rate limits, or return format. Minimal behavioral disclosure.

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?

Single sentence, no fluff. Efficiently conveys the tool's purpose and the parameter's role.

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?

For a simple tool with one required parameter and no output schema or annotations, the description sufficiently explains what the tool does and what input is needed. No gaps.

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

Parameters4/5

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

Schema coverage is 100% with description for slug. The description adds context by providing example slugs ('hubspot', 'apollo'), enhancing understanding beyond the schema alone.

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?

Clearly states verb 'get', resource 'starter prompt for a tool', and purpose 'immediately use it with your AI agent'. Distinguishes from sibling tools like compare_tools and get_tool_details.

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?

Implied usage when needing a starter prompt, but no explicit when-to-use or when-not-to-use, and no mention of alternatives among siblings.

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/akhilkannur/salestools-mcp'

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