Skip to main content
Glama
MarySuneela

Visa Design System MCP Server

by MarySuneela

get-guidelines

Retrieve design guidelines from Visa's Product Design System with optional category filtering to access component specifications and usage resources.

Instructions

Get design guidelines with optional category filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter guidelines by category

Implementation Reference

  • MCP tool handler that delegates to GuidelinesService.getGuidelines and formats the result as JSON response with count and applied filters.
    private async handleGetGuidelines(args: Record<string, any>): Promise<CallToolResult> {
      const guidelines = await this.guidelinesService.getGuidelines(args);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              guidelines,
              count: guidelines.length,
              filters: args
            }, null, 2)
          }
        ]
      };
    }
  • Core service method that retrieves guidelines from data cache, applies category/other filters via filterGuidelines, with circuit breaker and comprehensive error handling.
    @handleErrors
    async getGuidelines(options?: GuidelineSearchOptions): Promise<Guideline[]> {
      return this.circuitBreaker.execute(async () => {
        const cachedData = this.dataManager.getCachedData();
        
        if (!cachedData) {
          throw new DataError('No guidelines data available', [
            'Ensure data files are loaded',
            'Check data directory configuration'
          ], { service: 'GuidelinesService', method: 'getGuidelines' });
        }
    
        let guidelines = cachedData.guidelines;
    
        // Apply filters if provided
        if (options) {
          guidelines = this.filterGuidelines(guidelines, options);
        }
    
        return guidelines;
      }, { service: 'GuidelinesService', method: 'getGuidelines', options });
    }
  • Tool registration definition in getToolDefinitions(): includes name, description, and input schema for category filtering.
    {
      name: 'get-guidelines',
      description: 'Get design guidelines with optional category filtering',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Filter guidelines by category'
          }
        }
      }
    },
  • Input schema definition for the get-guidelines tool, allowing optional category filter.
    inputSchema: {
      type: 'object',
      properties: {
        category: {
          type: 'string',
          description: 'Filter guidelines by category'
        }
      }
  • Switch case routing get-guidelines tool calls to the specific handler function.
    case 'get-guidelines':
      return await this.handleGetGuidelines(args);
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 guidelines but doesn't cover aspects like pagination, rate limits, authentication needs, or what happens if no guidelines are found. This leaves significant gaps for an agent to understand the tool's behavior.

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 clearly states the tool's purpose and key feature (optional filtering). It's front-loaded with no wasted words, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral traits like whether it returns all guidelines or a subset. For a tool with no structured metadata, more context is needed to guide proper usage.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the 'category' parameter. The description adds minimal value by mentioning optional filtering but doesn't provide additional context like valid category values or examples beyond what the schema implies.

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 action ('Get') and resource ('design guidelines'), and mentions optional filtering by category. However, it doesn't differentiate from sibling tools like 'get-guideline-details' or 'search-guidelines', which limits its score.

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 like 'get-guideline-details' or 'search-guidelines'. It mentions optional filtering but doesn't specify contexts or exclusions for tool selection.

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