Skip to main content
Glama
akhilkannur

Salestools Club

by akhilkannur

get_tool_details

Retrieve comprehensive details about any sales tool, including API specs, authentication methods, AI capabilities, starter prompts, and MCP configuration.

Instructions

Get full details about a specific sales tool — API specs, auth methods, AI capabilities, starter prompts, MCP config, and more.

Input Schema

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

Implementation Reference

  • index.js:95-148 (handler)
    The handler function for the 'get_tool_details' tool. It takes a 'slug' argument, fetches the tool details from the SALESTOOLS API, and formats a detailed Markdown response including quick facts (category, API type, auth, free tier, MCP ready, webhooks, SDKs), AI capabilities, starter prompt, integrations (with MCP config), alternatives, and links.
    async function handleGetTool(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}\n\n`;
        text += `${tool.description || tool.oneLiner}\n\n`;
        text += `## Quick Facts\n`;
        text += `- **Category:** ${tool.category}\n`;
        text += `- **API Type:** ${(tool.apiType || []).join(', ') || 'N/A'}\n`;
        text += `- **Auth:** ${(tool.authMethod || []).join(', ') || 'N/A'}\n`;
        text += `- **Free Tier:** ${tool.hasFreeTier ? 'Yes' : 'No'}\n`;
        text += `- **MCP Ready:** ${tool.mcpReady ? 'Yes' : 'No'}\n`;
        text += `- **Webhooks:** ${tool.hasWebhooks ? 'Yes' : 'No'}\n`;
        if (tool.sdkLanguages?.length > 0) text += `- **SDKs:** ${tool.sdkLanguages.join(', ')}\n`;
        text += '\n';
    
        if (tool.aiCapabilities?.length > 0) {
          text += `## What AI Can Do With This\n`;
          text += tool.aiCapabilities.map(c => `- ${c}`).join('\n') + '\n\n';
        }
    
        if (tool.starterPrompt) {
          text += `## Starter Prompt\n\`\`\`\n${tool.starterPrompt}\n\`\`\`\n\n`;
        }
    
        if (tool.integrations?.length > 0) {
          text += `## Integrations\n`;
          for (const int of tool.integrations) {
            text += `- **${int.label || int.platform}:** ${int.url}\n`;
            if (int.mcpConfig) text += `  MCP Config:\n\`\`\`json\n${int.mcpConfig}\n\`\`\`\n`;
          }
          text += '\n';
        }
    
        if (tool.alternativeTo?.length > 0) {
          text += `## Alternatives To\n${tool.alternativeTo.join(', ')}\n\n`;
        }
    
        text += `## Links\n`;
        text += `- Website: ${tool.websiteUrl}\n`;
        if (tool.docsUrl) text += `- Docs: ${tool.docsUrl}\n`;
        if (tool.pricingUrl) text += `- Pricing: ${tool.pricingUrl}\n`;
        if (tool.githubUrl) text += `- GitHub: ${tool.githubUrl}\n`;
        text += `- Salestools Page: https://salestools.club/apis/${tool.slug}\n`;
    
        return { content: [{ type: "text", text: text.trim() }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Failed to fetch tool "${slug}": ${error.message}` }] };
      }
    }
  • The tool registration/schema definition for 'get_tool_details' within the ListToolsRequestSchema handler. It defines the tool's name, description, and input schema requiring a single 'slug' string parameter.
    {
      name: "get_tool_details",
      description: "Get full details about a specific sales tool — API specs, auth methods, AI capabilities, starter prompts, MCP config, and more.",
      inputSchema: {
        type: "object",
        properties: {
          slug: { type: "string", description: "The tool's slug (e.g., 'hubspot', 'apollo', 'lusha', 'pipedrive')" },
        },
        required: ["slug"],
      },
  • index.js:309-309 (registration)
    The route/registration mapping the tool name 'get_tool_details' to its handler function 'handleGetTool' inside the CallToolRequestSchema handler.
    case "get_tool_details": return handleGetTool(args);
Behavior3/5

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

With no annotations, the description carries full burden. It lists the content provided but does not disclose behavioral traits like idempotency, rate limits, or authentication requirements. The 'get' verb implies read-only, but explicit confirmation is missing.

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 with an enumerated list of content types. No redundant words, and key information is front-loaded.

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

Completeness4/5

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

Despite lacking an output schema, the description lists specific content categories, making it reasonably complete for a retrieval tool with one parameter. Minor gap: no mention of response format.

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?

Schema coverage is 100% with a clear description for 'slug'. The description does not add further meaning beyond the schema's examples. 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 uses a clear verb 'Get' and specifies the resource 'full details about a specific sales tool', listing concrete content like 'API specs, auth methods, AI capabilities'. This distinguishes it well from sibling tools like 'compare_tools' and 'get_starter_prompt'.

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 implies usage for obtaining detailed information about a single tool, which distinguishes it from siblings. However, it does not explicitly state when not to use it or provide alternatives.

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