Skip to main content
Glama
appian-design

Design System MCP Server

list-categories

Retrieve all available design system categories to organize and access components, layouts, and patterns for development projects.

Instructions

List all design system categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `list-categories` MCP tool, which lists keys from `designSystemData`.
    server.tool(
      "list-categories",
      "List all design system categories",
      {},
      async () => {
        const categories = Object.keys(designSystemData);
        
        return {
          content: [
            {
              type: "text",
              text: `Available design system categories: ${categories.join(", ")}`,
            },
          ],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, what format the output takes, if there are pagination considerations, rate limits, authentication requirements, or any side effects. The description is minimal and lacks important behavioral context.

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, efficient sentence that gets straight to the point with zero wasted words. It's perfectly front-loaded and appropriately sized for a simple listing tool with no parameters.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'categories' means in this design system context, what the output format looks like, or how this differs from related listing/search tools. The agent would need to guess about important behavioral and contextual aspects.

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 has zero parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't waste space discussing parameters that don't exist, earning a baseline 4 for this dimension.

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 clearly states the verb ('List') and resource ('design system categories'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'list-components' or explain what distinguishes categories from components in this design system context.

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?

The description provides no guidance about when to use this tool versus alternatives like 'list-components' or 'search-design-system'. There's no mention of prerequisites, context, or comparison with sibling tools that could help an agent choose appropriately.

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/appian-design/aurora-mcp'

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