Skip to main content
Glama
rlymbur

Amazon VPC Lattice MCP Server

by rlymbur

list_amazon_vpc_lattice_prompts

Retrieve available prompt templates for AWS VPC Lattice to streamline documentation and management tasks, enhancing AWS networking workflows.

Instructions

List all available prompt templates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'list_amazon_vpc_lattice_prompts' tool. Maps the imported prompts array to names and descriptions and returns as JSON.
    case 'list_amazon_vpc_lattice_prompts':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(prompts.map(p => ({
              name: p.name,
              description: p.description
            })), null, 2)
          }
        ]
      };
  • src/tools.ts:40-48 (registration)
    Tool registration entry in the exported tools array, including name, description, and input schema.
    {
      name: 'list_amazon_vpc_lattice_prompts',
      description: 'List all available prompt templates',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      },
    },
  • Helper data file exporting the prompts array used by the tool handler to list available prompts.
    export const prompts = [
      {
        name: 'create_github_pr',
        description: 'Create a GitHub pull request from current branch to main',
        template:
            '1. Get the current branch name using "git rev-parse --abbrev-ref HEAD"\n' +
            '2. Push the current branch to remote using "git push -u origin $(git rev-parse --abbrev-ref HEAD)"\n' +
            '3. Use the GitHub MCP server to create a pull request from the current branch to main branch on aws/aws-application-networking-k8s',
        parameters: []
      },
      {
        name: 'setup_eks_controller',
        description: 'Guide for setting up the AWS Application Networking Controller for Kubernetes',
        template: 'Run "make setup" and assist with any resulting errors.',
        parameters: ['cluster_name', 'region', 'k8s_version']
      },
      {
        name: 'run_eks_controller_tests',
        description: 'Run tests for the AWS Application Networking Controller',
        template:
            'Request a test_type from the user. Based on the test_type perform the following tasks. If test_type is unit, ' +
            'run "make test" in the current directory and summarize the results. If test_type is integration, complete the ' +
            'following steps:/n' +
            '1. Kill any processes running in the current terminal and then run "make run".\n' +
            '2. Open a new terminal window and run "make e2e-clean && export FOCUS=$test_focus && export SECONDARY_ACCOUNT_TEST_ROLE_ARN=$secondary_account && make e2e-test" and summarize the results.\n' +
            '3. Return to the original terminal and kill any running processes. If the test_type is not provided, run the steps described for a unit test type first, then the steps described for the integration test type.',
        parameters: ['test_type', 'test_focus', 'secondary_account']
      },
      {
        name: 'eks_controller_issue_solution',
        description: 'Create a solution for an AWS Application Networking Controller GitHub issue',
        template:
            'Create a solution for an AWS Application Networking Controller GitHub issue with the following steps:\n' +
            '1. Request an issue_number from the user. Use the GitHub get_issue tool to understand the issue.\n' +
            '2. Provide a summary of the proposed code changes. Ask the user if they would like to proceed. If they have not chosen to proceed, stop here.\n' +
            '3. Create a new branch locally by running "git checkout -b $branch_name" with an appropriate branch name.\n' +
            '4. Proceed with the code changes using best practices. Ask the user for clarification if required.\n' +
            '5. Ask the user if they would like to create unit tests based on the diff of changes. Append these tests to the existing test file if applicable.\n' +
            '6. Before commiting changes to the local branch, run "source ~/.bashrc && make presubmit" to confirm unit tests pass.',
        parameters: ['issue_number']
      },
      {
        name: 'review_github_pr',
        description: 'Perform a comprehensive code review of a GitHub pull request',
        template:
            'Perform a code review for: {pr_url} by providing specific recommendations for improvements in each of the following areas:\n' +
            '1. Code Quality (Clean and maintainable code, Follows project conventions, No code smells or anti-patterns, Proper error handling, Performance considerations)\n' +
            '2. Testing (Adequate test coverage, Test cases cover edge cases, Integration test considerations, Test documentation)\n' +
            '3. Security (No security vulnerabilities, Secure coding practices, Proper input validation, Authentication/authorization checks)\n' +
            '4. Documentation (Clear inline comments, Updated README/docs, API documentation if applicable, Architecture changes documented)\n' +
            '5. Design (Follows SOLID principles, Appropriate abstractions, Interface consistency, Scalability considerations)\n' +
            '6. Dependencies (Proper version management, No conflicting dependencies, Security of dependencies)',
        parameters: ['pr_url']
      },
      {
        name: 'generate_docs',
        description: 'Generate documentation for code or APIs',
        template: 'Generate documentation for: {code}\n\nInclude:\n- Overview\n- Parameters\n- Return values\n- Example usage',
        parameters: ['code']
      },
      {
        name: 'review_security',
        description: 'Review code or architecture for security concerns',
        template: 'Perform a security review of the code base. Check for vulnerabilities, best practices, and compliance issues',
        parameters: ['target']
      }
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List all available prompt templates' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or details the format of the output. For a tool with zero annotation coverage, this is insufficient.

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 directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, 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.

Completeness3/5

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

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally adequate but lacks completeness. It doesn't explain what 'prompt templates' are, how they're structured, or what the output looks like, which could hinder an agent's ability to use this tool effectively in context with siblings.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information beyond what the schema provides.

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 ('List') and resource ('all available prompt templates'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_amazon_vpc_lattice_prompts' or 'get_source_prompts', which likely retrieve specific prompts rather than listing all templates.

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 on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'get_amazon_vpc_lattice_prompts' (which might retrieve specific prompts) or 'list_sources' (which might list different resources), leaving the agent without context 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

Related 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/rlymbur/amazon-vpc-lattice-mcp-server'

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