Skip to main content
Glama
akhilkannur

Salestools Club

by akhilkannur

compare_tools

Compare two sales tools side-by-side on API type, authentication, pricing, MCP support, AI capabilities, and SDKs.

Instructions

Compare two sales tools side-by-side — API type, auth, pricing, MCP support, AI capabilities, and SDKs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool1YesSlug of the first tool (e.g., 'hubspot')
tool2YesSlug of the second tool (e.g., 'pipedrive')

Implementation Reference

  • The main handler function for the 'compare_tools' tool. Fetches details for two tools by slug from the API and produces a side-by-side comparison table covering category, API type, auth, free tier, MCP readiness, webhooks, SDKs, AI capabilities, and links.
    async function handleCompare(args) {
      const { tool1, tool2 } = args;
      try {
        const [t1, t2] = await Promise.all([
          fetchJSON(`${BASE_URL}/api/tools/${encodeURIComponent(tool1)}`),
          fetchJSON(`${BASE_URL}/api/tools/${encodeURIComponent(tool2)}`),
        ]);
    
        if (t1.error) return { content: [{ type: "text", text: `Tool "${tool1}" not found.` }] };
        if (t2.error) return { content: [{ type: "text", text: `Tool "${tool2}" not found.` }] };
    
        let text = `# ${t1.name} vs ${t2.name}\n\n`;
        text += `| Feature | ${t1.name} | ${t2.name} |\n`;
        text += `|---------|${'-'.repeat(t1.name.length + 2)}|${'-'.repeat(t2.name.length + 2)}|\n`;
        text += `| Category | ${t1.category} | ${t2.category} |\n`;
        text += `| API Type | ${(t1.apiType || []).join(', ')} | ${(t2.apiType || []).join(', ')} |\n`;
        text += `| Auth | ${(t1.authMethod || []).join(', ')} | ${(t2.authMethod || []).join(', ')} |\n`;
        text += `| Free Tier | ${t1.hasFreeTier ? '✅' : '❌'} | ${t2.hasFreeTier ? '✅' : '❌'} |\n`;
        text += `| MCP Ready | ${t1.mcpReady ? '✅' : '❌'} | ${t2.mcpReady ? '✅' : '❌'} |\n`;
        text += `| Webhooks | ${t1.hasWebhooks ? '✅' : '❌'} | ${t2.hasWebhooks ? '✅' : '❌'} |\n`;
        text += `| SDKs | ${(t1.sdkLanguages || []).join(', ') || 'None'} | ${(t2.sdkLanguages || []).join(', ') || 'None'} |\n`;
        text += '\n';
    
        if (t1.aiCapabilities?.length > 0 || t2.aiCapabilities?.length > 0) {
          text += `## AI Capabilities\n`;
          text += `**${t1.name}:** ${(t1.aiCapabilities || []).join(', ') || 'Not listed'}\n`;
          text += `**${t2.name}:** ${(t2.aiCapabilities || []).join(', ') || 'Not listed'}\n\n`;
        }
    
        text += `## Links\n`;
        text += `- ${t1.name}: https://salestools.club/apis/${t1.slug}\n`;
        text += `- ${t2.name}: https://salestools.club/apis/${t2.slug}\n`;
        text += `- Compare page: https://salestools.club/vs/${t1.slug}-vs-${t2.slug}\n`;
    
        return { content: [{ type: "text", text: text.trim() }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Comparison failed: ${error.message}` }] };
      }
    }
  • Registration of the 'compare_tools' tool schema, defining its name, description, and inputSchema (requiring two strings: tool1 and tool2 slugs).
    {
      name: "compare_tools",
      description: "Compare two sales tools side-by-side — API type, auth, pricing, MCP support, AI capabilities, and SDKs.",
      inputSchema: {
        type: "object",
        properties: {
          tool1: { type: "string", description: "Slug of the first tool (e.g., 'hubspot')" },
          tool2: { type: "string", description: "Slug of the second tool (e.g., 'pipedrive')" },
        },
        required: ["tool1", "tool2"],
      },
    },
  • index.js:310-310 (registration)
    The dispatcher/call-router that matches the tool name 'compare_tools' to the handleCompare function.
    case "compare_tools": return handleCompare(args);
  • The fetchJSON helper used by handleCompare to fetch tool data from the external API.
    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 are provided, so the description carries the full burden. It explains what the tool does (compare attributes) but does not disclose any behavioral traits such as whether it fetches live data, if authentication is required, or potential rate limits. The description gives minimal behavioral context beyond the action.

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?

The description is a single sentence that efficiently states the action and lists key aspects. Every word adds value, with no redundancy or filler. It front-loads the purpose.

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?

Given that there is no output schema and parameters are simple strings, the description adequately explains what the tool compares (specific attributes). It is complete enough for an agent to understand the tool's capabilities, though it could briefly mention the return format or potential errors.

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 description coverage is 100% (both 'tool1' and 'tool2' have clear descriptions as tool slugs). The description adds no parameter-specific information beyond the schema, so it meets the baseline without further enrichment.

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 clearly states the tool compares two sales tools side-by-side and lists the specific attributes compared (API type, auth, pricing, MCP support, AI capabilities, SDKs). This distinguishes it from sibling tools like get_tool_details (single tool details) and search_sales_tools (listing/filtering).

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 when a side-by-side comparison of two specific tools is needed. However, it does not explicitly state when not to use it or mention alternatives (e.g., for single tool details use get_tool_details). The context is clear but lacks exclusions.

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