Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

list_categories

List all 45 software categories, including their unique slugs and human-readable display names.

Instructions

List all 45 supported software categories with their slugs and display names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the 'list_categories' tool logic. Maps over the CATEGORIES constant array and formats each category with its rank, name, and slug. Returns a string listing all 45 supported categories.
    function listCategoriesFn() {
      const lines = CATEGORIES.map((c, i) =>
        `${String(i + 1).padStart(2)}. ${c.name.padEnd(35)} (${c.slug})`
      );
      return `Supported categories (${CATEGORIES.length} total):\n\n${lines.join('\n')}`;
  • Schema / tool definition for 'list_categories'. Declares the tool name, description ('List all 45 supported software categories with their slugs and display names.'), and an empty input schema (no parameters required).
    {
      name: 'list_categories',
      description: 'List all 45 supported software categories with their slugs and display names.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • index.js:446-459 (registration)
    Dispatch function that routes the tool name 'list_categories' to its handler function listCategoriesFn() in a switch statement within callTool().
    // --- Dispatch ---
    
    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}`);
      }
  • CATEGORIES constant array defining all 45 supported software categories with slug and name pairs. This data is used by the listCategoriesFn handler to produce the list of categories.
    const CATEGORIES = [
      { slug: 'ai-tools', name: 'AI Tools' },
      { slug: 'llm', name: 'Large Language Models' },
      { slug: 'ai-coding', name: 'AI Coding' },
      { slug: 'ai-writing', name: 'AI Writing' },
      { slug: 'ai-image', name: 'AI Image Generation' },
      { slug: 'ai-video', name: 'AI Video' },
      { slug: 'ai-audio', name: 'AI Audio' },
      { slug: 'project-management', name: 'Project Management' },
      { slug: 'crm', name: 'CRM' },
      { slug: 'email-marketing', name: 'Email Marketing' },
      { slug: 'customer-support', name: 'Customer Support' },
      { slug: 'analytics', name: 'Analytics' },
      { slug: 'design-tools', name: 'Design Tools' },
      { slug: 'video-conferencing', name: 'Video Conferencing' },
      { slug: 'cloud-hosting', name: 'Cloud Hosting' },
      { slug: 'devops', name: 'DevOps' },
      { slug: 'security', name: 'Security' },
      { slug: 'cloud-security', name: 'Cloud Security' },
      { slug: 'iam', name: 'Identity and Access Management' },
      { slug: 'siem', name: 'SIEM' },
      { slug: 'edr', name: 'Endpoint Detection and Response' },
      { slug: 'vulnerability-management', name: 'Vulnerability Management' },
      { slug: 'compliance', name: 'Compliance' },
      { slug: 'erp', name: 'ERP' },
      { slug: 'hr-tools', name: 'HR Tools' },
      { slug: 'accounting', name: 'Accounting' },
      { slug: 'legal-tech', name: 'Legal Tech' },
      { slug: 'data-visualization', name: 'Data Visualization' },
      { slug: 'bi-tools', name: 'Business Intelligence' },
      { slug: 'database', name: 'Database' },
      { slug: 'vector-db', name: 'Vector Database' },
      { slug: 'api-management', name: 'API Management' },
      { slug: 'payment-processing', name: 'Payment Processing' },
      { slug: 'e-commerce', name: 'E-Commerce' },
      { slug: 'email-infrastructure', name: 'Email Infrastructure' },
      { slug: 'monitoring', name: 'Monitoring' },
      { slug: 'logging', name: 'Logging' },
      { slug: 'feature-flags', name: 'Feature Flags' },
      { slug: 'a-b-testing', name: 'A/B Testing' },
      { slug: 'crypto-exchanges', name: 'Crypto Exchanges' },
      { slug: 'crypto-trading-bots', name: 'Crypto Trading Bots' },
      { slug: 'defi-tools', name: 'DeFi Tools' },
      { slug: 'dex', name: 'Decentralized Exchanges' },
      { slug: 'nft-tools', name: 'NFT Tools' },
      { slug: 'vpn', name: 'VPN' },
      { slug: 'password-managers', name: 'Password Managers' },
    ];
Behavior3/5

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

No annotations are provided, and the description does not explicitly state behavioral traits such as idempotency, safety, or performance. However, the tool's simplicity (no parameters) weakly implies a safe, read-only operation.

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, well-structured sentence that conveys all essential information without wasted words. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple parameterless tool without an output schema, the description fully covers what the agent needs to know: the action, the scope, and the return content. No gaps remain.

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?

With zero parameters, the schema provides no information; the description adds value by specifying the output fields (slugs and display names), which is meaningful context for the agent.

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 (List), the resource (all 45 supported software categories), and the output details (slugs and display names). It distinguishes from sibling list_category by implying it returns all categories.

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 retrieving all categories, and the existence of a sibling list_category suggests when to use the plural vs singular form, but no explicit 'when not to use' or alternatives are given.

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