Skip to main content
Glama

categories

List available ASCII art and kaomoji collections to browse organized visual content for AI agents, CLI tools, and chatbots.

Instructions

List all categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool 'categories' registration and handler. The tool is registered with server.tool() and the handler logic directly calls listCategories() to get all categories and returns them as a comma-separated string.
    server.tool('categories', 'List all categories.', {}, async () => {
      const cats = listCategories();
      return { content: [{ type: 'text', text: cats.join(', ') }] };
    });
  • listCategories() function implementation in the store module. This function retrieves all unique categories from the ASCII art entries by delegating to uniqueCategories().
    export function listCategories(): string[] {
      return uniqueCategories(entries);
    }
  • uniqueCategories() helper function that extracts unique category values from an array of Searchable entries using a Set to deduplicate.
    export function uniqueCategories<T extends Searchable>(entries: T[]): string[] {
      return [...new Set(entries.map((e) => e.category))];
    }
  • src/mcp.ts:1-12 (registration)
    Import statements showing the listCategories function is imported from the store module, establishing the dependency chain for the categories tool.
    #!/usr/bin/env node
    import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
    import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
    import { z } from 'zod';
    
    import { loadIndex, search, getById, getRandom, listCategories, listAll, toResult, addArt, deleteArt } from './store.js';
    import { loadKaomoji, searchKaomoji, getRandomKaomoji, listKaomojiCategories, getKaomojiByCategory, toKaomojiResult } from './kaomoji.js';
    import { MAX_NAME_LENGTH, MAX_TAG_LENGTH, MAX_TAGS, MAX_DESCRIPTION_LENGTH, SIZE_LIMITS, DEFAULT_SIZE } from './constants.js';
    import { resolveImageInput } from './resolve.js';
    import { convertImage } from './converter.js';
    import { renderBanner, BANNER_FONTS } from './banner.js';
    import type { ArtSize } from './types.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description does not confirm safety, mention pagination, describe the return structure, or explain what these categories represent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at only three words. It is front-loaded with the essential action and resource. However, given the lack of annotations and presence of siblings, it borders on under-specification rather than optimal conciseness.

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

Completeness3/5

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

For a parameterless tool, the description meets minimum viability by stating the core function. However, gaps remain regarding the nature of the categories (are they user-created, system-defined?), their relationship to other entities, and the expected output format.

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?

The tool accepts zero parameters, which per the evaluation rubric establishes a baseline score of 4. The empty input schema requires no additional semantic clarification from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description uses a specific verb ('List') and identifies the resource ('categories'), clearly indicating it retrieves a collection. However, it fails to differentiate from the sibling 'list' tool, leaving ambiguity about when to use this specific endpoint versus the general list tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided regarding when to use this tool versus alternatives. Given the presence of a sibling 'list' tool and a 'search' tool, the description should clarify the specific scope of these categories.

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/rxolve/artscii'

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