Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

list_category

Browse software tools in a specific category with pricing overview, ratings, and free plan filter. Sort by rating or starting price.

Instructions

Browse all tools in a specific software category with pricing overview. Supports sorting and free-only filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory slug (e.g., "llm", "ai-coding", "crm")
sort_byNoSort field: "rating" (default) or "startingPrice"
free_onlyNoIf true, return only tools with a free plan (default: false)

Implementation Reference

  • Tool definition (name + inputSchema) for 'list_category' — defines the category, sort_by, and free_only parameters.
    {
      name: 'list_category',
      description: 'Browse all tools in a specific software category with pricing overview. Supports sorting and free-only filtering.',
      inputSchema: {
        type: 'object',
        properties: {
          category: { type: 'string', description: 'Category slug (e.g., "llm", "ai-coding", "crm")' },
          sort_by: { type: 'string', description: 'Sort field: "rating" (default) or "startingPrice"' },
          free_only: { type: 'boolean', description: 'If true, return only tools with a free plan (default: false)' },
        },
        required: ['category'],
      },
    },
  • The actual handler/function that executes the 'list_category' tool logic — filters tools by category, sorts by rating or price, supports free-only filter, and formats the output.
    async function listCategory(args) {
      const { category, sort_by = 'rating', free_only = false } = args;
      const allTools = await getAllTools();
    
      let filtered = allTools.filter(t => t.category === category || t.categoryName === category);
      if (filtered.length === 0) {
        return `No tools found for category "${category}". Use list_categories to see available category slugs.`;
      }
      if (free_only) filtered = filtered.filter(t => t.freePlan);
      if (sort_by === 'startingPrice') {
        filtered.sort((a, b) => (a.startingPrice ?? Infinity) - (b.startingPrice ?? Infinity));
      } else {
        filtered.sort((a, b) => (b.rating ?? 0) - (a.rating ?? 0));
      }
    
      const header = `Category: ${filtered[0]?.categoryName || category} (${filtered.length} tools${free_only ? ', free only' : ''}, sorted by ${sort_by})`;
      const lines = filtered.map((t, i) =>
        `${i + 1}. ${t.name} | Rating: ${t.rating ?? 'N/A'}/5 | Free: ${t.freePlan ? 'Yes' : 'No'} | Price: ${formatPrice(t.startingPrice)} | ${toolURL(t.slug)}`
      );
      return `${header}\n\n${lines.join('\n')}`;
    }
  • index.js:448-459 (registration)
    Dispatch switch-case that routes 'list_category' tool calls to the listCategory 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}`);
      }
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool supports sorting and free-only filtering, and browsing implies a read operation. However, it does not explicitly state it has no side effects or require special permissions.

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 short sentences with no wasted words. The first sentence captures the main purpose, and the second adds key features. 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?

For a simple listing tool with 3 parameters and no output schema, the description covers the main functionality and features. It misses details on output structure or limitations, but is reasonably complete for the complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds context about 'pricing overview' and frames the parameters (sorting, free-only) within the tool's purpose, providing extra meaning beyond the schema.

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 verb 'browse' and the resource 'tools in a specific software category', with explicit mention of pricing overview, sorting, and filtering. This distinguishes it from sibling tools like compare_tools, get_alternatives, 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 use for browsing tools in a category but does not explicitly state when to use this over siblings like search_tools or get_tool. No when-not or alternative 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