Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

search_tools

Search over 508 software products by name or keyword to find their category, rating, free plan availability, starting price, and URL.

Instructions

Search 508+ software products by name or keyword. Returns name, category, rating, free plan availability, starting price, and ComparEdge URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string (product name, keyword, or use case)
limitNoMaximum number of results to return (default: 5)

Implementation Reference

  • The main handler function for search_tools. Accepts query and optional limit, fetches all tools, scores by relevance (name, slug, description, category), filters, sorts, and returns formatted results.
    async function searchTools(args) {
      const { query, limit = 5 } = args;
      const q = query.toLowerCase();
      const allTools = await getAllTools();
    
      // Score each tool by relevance
      const scored = allTools
        .map(t => {
          let score = 0;
          const name = (t.name || '').toLowerCase();
          const slug = (t.slug || '').toLowerCase();
          const desc = (t.description || '').toLowerCase();
          const cat  = (t.categoryName || t.category || '').toLowerCase();
    
          if (name === q) score += 100;
          else if (name.startsWith(q)) score += 60;
          else if (name.includes(q)) score += 40;
          if (slug.includes(q)) score += 30;
          if (desc.includes(q)) score += 20;
          if (cat.includes(q)) score += 15;
    
          return { t, score };
        })
        .filter(x => x.score > 0)
        .sort((a, b) => b.score - a.score || (b.t.rating ?? 0) - (a.t.rating ?? 0))
        .slice(0, limit)
        .map(x => x.t);
    
      if (scored.length === 0) {
        return `No results found for "${query}".`;
      }
    
      const lines = scored.map((t, i) => {
        const rating = t.rating ? `${t.rating}/5` : 'N/A';
        const free   = t.freePlan ? 'Yes' : 'No';
        const price  = t.startingPrice !== undefined ? formatPrice(t.startingPrice) : 'N/A';
        return [
          `${i + 1}. ${t.name} (${t.slug})`,
          `   Category: ${t.categoryName || t.category || 'N/A'}`,
          `   Rating: ${rating} | Free plan: ${free} | Starting price: ${price}`,
          `   URL: ${toolURL(t.slug)}`,
        ].join('\n');
      });
    
      return `Search results for "${query}" (${scored.length} found):\n\n${lines.join('\n\n')}`;
    }
  • Input schema definition for search_tools: requires 'query' (string), optional 'limit' (number, default 5).
    name: 'search_tools',
    description: 'Search 508+ software products by name or keyword. Returns name, category, rating, free plan availability, starting price, and ComparEdge URL.',
    inputSchema: {
      type: 'object',
      properties: {
        query: { type: 'string', description: 'Search query string (product name, keyword, or use case)' },
        limit: { type: 'number', description: 'Maximum number of results to return (default: 5)' },
      },
      required: ['query'],
    },
  • index.js:448-450 (registration)
    Dispatch table in callTool() that routes 'search_tools' to the searchTools handler function.
    async function callTool(name, args) {
      switch (name) {
        case 'search_tools':    return searchTools(args);
  • index.js:483-484 (registration)
    tools/list handler returns TOOL_DEFINITIONS array which includes the search_tools definition.
    if (method === 'tools/list') {
      return makeResponse(id, { tools: TOOL_DEFINITIONS });
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It lists the output fields but does not disclose behavioral traits such as whether the operation is read-only, rate limits, or authentication requirements. The description is partially transparent but incomplete.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the tool's action and output.

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 no output schema and no annotations, the description competently covers purpose, output fields, and parameters. It lacks details on pagination or error handling, but for a straightforward search tool, it is largely sufficient.

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 both parameters described. The description adds minimal extra context (the product count '508+'), but does not elaborate on parameter format or constraints beyond what the schema already provides.

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 searches 508+ software products by name or keyword and specifies the returned fields (name, category, rating, etc.). This distinguishes it from siblings like 'get_tool' or 'compare_tools', which have different scopes.

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 searching products, but does not explicitly state when to use this tool versus siblings like 'compare_tools' or 'get_alternatives'. No exclusions or alternative conditions 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