Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

compare_tools

Compare two software products side-by-side to view pricing, features, ratings, and key differences.

Instructions

Side-by-side structured comparison of two software products. Returns pricing, features, ratings, and key differences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool1YesSlug of the first tool to compare
tool2YesSlug of the second tool to compare

Implementation Reference

  • Schema definition for compare_tools tool: defines name, description, and inputSchema with required tool1/tool2 slug strings.
    {
      name: 'compare_tools',
      description: 'Side-by-side structured comparison of two software products. Returns pricing, features, ratings, and key differences.',
      inputSchema: {
        type: 'object',
        properties: {
          tool1: { type: 'string', description: 'Slug of the first tool to compare' },
          tool2: { type: 'string', description: 'Slug of the second tool to compare' },
        },
        required: ['tool1', 'tool2'],
      },
    },
  • Handler function for compare_tools. Fetches all tools, finds both by slug, and returns a side-by-side formatted comparison including category, rating, free plan, starting price, plans, and URLs.
    async function compareTools(args) {
      const { tool1, tool2 } = args;
      const allTools = await getAllTools();
    
      const t1 = allTools.find(x => x.slug === tool1);
      const t2 = allTools.find(x => x.slug === tool2);
    
      if (!t1) return `Tool "${tool1}" not found. Use search_tools to find the correct slug.`;
      if (!t2) return `Tool "${tool2}" not found. Use search_tools to find the correct slug.`;
    
      const lines = [
        `Comparison: ${t1.name} vs ${t2.name}`,
        '',
        fmtRow('Field', t1.name.slice(0, 20), t2.name.slice(0, 20)),
        '-'.repeat(70),
        fmtRow('Category', t1.categoryName || t1.category, t2.categoryName || t2.category),
        fmtRow('Rating', t1.rating ? `${t1.rating}/5` : 'N/A', t2.rating ? `${t2.rating}/5` : 'N/A'),
        fmtRow('Free plan', t1.freePlan ? 'Yes' : 'No', t2.freePlan ? 'Yes' : 'No'),
        fmtRow('Starting price', formatPrice(t1.startingPrice), formatPrice(t2.startingPrice)),
        fmtRow('Verified at', t1.verifiedAt || 'N/A', t2.verifiedAt || 'N/A'),
      ];
    
      // Plans for t1
      const p1 = t1.plans;
      if (p1 && p1.length > 0) {
        lines.push(`\n${t1.name} plans:`);
        p1.forEach(p => lines.push(`  - ${p.name}: ${formatPrice(p.price)}`));
      }
    
      // Plans for t2
      const p2 = t2.plans;
      if (p2 && p2.length > 0) {
        lines.push(`\n${t2.name} plans:`);
        p2.forEach(p => lines.push(`  - ${p.name}: ${formatPrice(p.price)}`));
      }
    
      lines.push(`\n${t1.name} URL: ${toolURL(tool1)}`);
      lines.push(`${t2.name} URL: ${toolURL(tool2)}`);
      lines.push(`Full comparison: ${SITE_BASE}/compare/${tool1}-vs-${tool2}`);
      return lines.join('\n');
    }
  • index.js:448-460 (registration)
    Dispatch registration in callTool() switch statement routing the name 'compare_tools' to the compareTools handler function.
    async function callTool(name, args) {
      switch (name) {
        case 'search_tools':    return searchTools(args);
        case 'get_tool':        return getTool(args);
        case 'compare_tools':   return compareTools(args);
        case 'list_category':   return listCategory(args);
        case 'get_alternatives':return getAlternatives(args);
        case 'get_pricing':     return getPricing(args);
        case 'get_leaderboard': return getLeaderboard(args);
        case 'list_categories': return listCategoriesFn();
        default: throw new Error(`Unknown tool: ${name}`);
      }
    }
  • fmtRow helper used by compareTools to format a padded two-column row for the comparison output.
    function fmtRow(label, v1, v2) {
      return `${label.padEnd(22)} ${String(v1 ?? 'N/A').slice(0, 22).padEnd(22)} ${String(v2 ?? 'N/A').slice(0, 22)}`;
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It lists return categories (pricing, features, ratings, differences) but does not disclose read-only nature, required permissions, data freshness, or any side effects. This is adequate but lacks depth for a data-fetching tool.

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 is front-loaded with the action and scope, then lists outputs. No superfluous words; every phrase earns its place.

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 the absence of an output schema, the description adequately explains the return structure (pricing, features, ratings, differences). However, it does not clarify what constitutes a 'slug' or how to discover valid slugs, which is a minor gap. Sibling tools suggest a ecosystem, but reliance on external knowledge is noted.

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%, with descriptions for each parameter ('Slug of the first/second tool to compare'). The description adds no further detail beyond the schema, so it meets baseline expectations but does not enhance understanding of slug format or valid values.

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 operation (side-by-side structured comparison), the resource (two software products), and the output (pricing, features, ratings, key differences). It effectively distinguishes from sibling tools like get_alternatives and get_pricing by specifying the comparative nature and return types.

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 for comparing two specific tools but does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_alternatives for indirect alternatives, search_tools for browsing). No exclusion criteria or prerequisites 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/comparedge/mcp-server-comparedge'

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