Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

get_tool

Get full details for a software tool by slug, including name, description, category, rating, pricing, features, and URL.

Instructions

Retrieve full details for a specific software tool by its slug. Returns name, description, category, rating, all pricing plans, features, and ComparEdge URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesTool slug identifier (e.g., "openai", "notion", "github-copilot")

Implementation Reference

  • index.js:81-91 (registration)
    Registration of the 'get_tool' tool in the TOOL_DEFINITIONS array with its name, description, and inputSchema (slug required).
    {
      name: 'get_tool',
      description: 'Retrieve full details for a specific software tool by its slug. Returns name, description, category, rating, all pricing plans, features, and ComparEdge URL.',
      inputSchema: {
        type: 'object',
        properties: {
          slug: { type: 'string', description: 'Tool slug identifier (e.g., "openai", "notion", "github-copilot")' },
        },
        required: ['slug'],
      },
    },
  • Handler function that retrieves full details for a specific software tool by its slug. Fetches tools and pricing data, looks up the tool by slug, and formats a response with name, description, category, rating, free plan, pricing plans, features, and URLs.
    async function getTool(args) {
      const { slug } = args;
      const [allTools, allPricing] = await Promise.all([getAllTools(), getAllPricing()]);
    
      const t = allTools.find(x => x.slug === slug);
      if (!t) return `Tool with slug "${slug}" not found. Use search_tools to find the correct slug.`;
    
      const pricing = allPricing.find(x => x.slug === slug);
    
      const lines = [
        `Name: ${t.name}`,
        `Slug: ${t.slug}`,
        `Category: ${t.categoryName || t.category || 'N/A'}`,
        `Description: ${t.description || 'N/A'}`,
        `Rating: ${t.rating ? `${t.rating}/5` : 'N/A'}`,
        `Free plan: ${t.freePlan ? 'Yes' : 'No'}`,
        `Starting price: ${t.startingPrice !== undefined ? formatPrice(t.startingPrice) : 'N/A'}`,
        `Verified at: ${t.verifiedAt || t.lastUpdated || 'N/A'}`,
      ];
    
      const plans = pricing?.plans || t.plans;
      if (plans && plans.length > 0) {
        lines.push('\nPricing plans:');
        plans.forEach(p => {
          const price = p.price !== undefined ? formatPrice(p.price) : 'N/A';
          const hl = Array.isArray(p.highlights) ? p.highlights.slice(0, 3).join(', ') : '';
          lines.push(`  - ${p.name}: ${price}${hl ? ` | ${hl}` : ''}`);
        });
      }
    
      if (t.features && t.features.length > 0) {
        lines.push('\nKey features:');
        t.features.slice(0, 10).forEach(f => lines.push(`  - ${f}`));
      }
    
      lines.push(`\nComparEdge URL: ${toolURL(slug)}`);
      lines.push(`Pricing details: ${pricingURL(slug)}`);
      return lines.join('\n');
    }
  • index.js:448-460 (registration)
    Dispatch switch-case that routes the 'get_tool' tool call to the getTool 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}`);
      }
    }
  • Helper function to format prices used by getTool.
    function formatPrice(price) {
      if (price === null || price === undefined) return 'N/A';
      if (price === 0) return 'Free';
      return `$${price}/mo`;
    }
  • Helper functions to generate tool and pricing URLs used by getTool.
    function toolURL(slug) {
      return `${SITE_BASE}/tools/${slug}`;
    }
    
    function pricingURL(slug) {
      return `${SITE_BASE}/pricing/${slug}-pricing`;
    }
Behavior3/5

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

No annotations provided, so the description carries the burden. It describes a read operation without detailing potential issues like rate limits, authentication, or error handling. The description is adequate but not rich.

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?

Two sentences with no wasted words. The first sentence provides the core purpose and key, the second lists returned fields. Front-loaded and efficient.

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?

Without an output schema, the description lists the returned fields (name, description, etc.), which is reasonably complete for a detail retrieval. However, it could specify that the result is a single object or include structure details.

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 'slug' with description and examples. The tool description only reiterates 'by its slug', adding no extra meaning beyond the schema. Baseline 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.

Purpose5/5

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

The description clearly states the action ('Retrieve full details'), the resource ('specific software tool'), and the key ('by its slug'). It lists the returned fields, distinguishing it from siblings like 'compare_tools' or 'search_tools'.

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 retrieving details by slug but does not explicitly state when to use this tool versus alternatives like 'compare_tools' or 'search_tools'. No when-not-to-use guidance is provided.

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