Skip to main content
Glama
MarySuneela

Visa Design System MCP Server

by MarySuneela

get-design-token-categories

Retrieve all available design token categories from Visa's Design System to access structured styling resources for consistent UI development.

Instructions

Get all available design token categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic: Retrieves all design tokens, extracts unique categories using a Set, sorts them alphabetically, and returns the list.
    async getTokenCategories(): Promise<string[]> {
      const tokens = await this.getTokens();
      const categories = new Set(tokens.map(token => token.category));
      return Array.from(categories).sort();
    }
  • MCP server tool handler: Calls DesignTokenService.getTokenCategories() and formats the result as JSON text content with category list and count.
    private async handleGetDesignTokenCategories(args: Record<string, any>): Promise<CallToolResult> {
      const categories = await this.designTokenService.getTokenCategories();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              categories,
              count: categories.length
            }, null, 2)
          }
        ]
      };
    }
  • Tool registration in getToolDefinitions(): Defines the tool name, description, and empty input schema (no parameters required).
    {
      name: 'get-design-token-categories',
      description: 'Get all available design token categories',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Input schema definition: Accepts an empty object (no required parameters).
    inputSchema: {
      type: 'object',
      properties: {}
    }
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. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns paginated results, or describes the format of the returned categories.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

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 zero-parameter tool with no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks details on behavior, output format, or usage context, leaving gaps that could hinder an agent's understanding.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate here, earning a baseline score of 4 for not introducing confusion.

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 tool's purpose with a specific verb ('Get') and resource ('design token categories'), making it immediately understandable. It distinguishes itself from siblings like 'get-design-token-details' by focusing on categories rather than details, though it doesn't explicitly mention this distinction.

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 on when to use this tool versus alternatives. It doesn't mention when to prefer this over 'get-design-tokens' or 'get-design-token-details', nor does it specify any prerequisites or context for usage.

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/MarySuneela/mcp-vpds'

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