Skip to main content
Glama
rlymbur

Amazon VPC Lattice MCP Server

by rlymbur

list_sources

Access and manage AWS VPC Lattice information by listing available sources with URLs and sample prompts for AWS networking documentation.

Instructions

List all available sources with their URLs and sample prompts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list_sources' tool, which serializes a list of source names and URLs from the imported 'sources' data into JSON format and returns it as tool response content.
    case 'list_sources':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(sources.map(s => ({
              name: s.name,
              url: s.url
            })), null, 2)
          }
        ]
      };
  • src/tools.ts:16-24 (registration)
    Tool registration entry for 'list_sources' in the exported 'tools' array, defining the tool's name, description, and empty input schema (no parameters required).
    {
      name: 'list_sources',
      description: 'List all available sources with their URLs and sample prompts',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      },
    },
  • Input schema for the 'list_sources' tool, specifying an empty object (no input parameters).
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
  • Exported 'sources' data array providing the list of sources with names, URLs, and prompts, used by the list_sources handler.
    export const sources = [
      {
        name: 'AWS Documentation',
        url: 'https://docs.aws.amazon.com',
        prompts: [
          'What are the key features of {service}?',
          'How do I configure {service} for {use_case}?',
          'What are the best practices for using {service}?'
        ]
      },
      {
        name: 'AWS Gateway API Controller for VPC Lattice',
        url: 'https://github.com/aws/aws-application-networking-k8s',
        prompts: [
          'Does the EKS controller support {feature}',
          'Show me {type} issues in the EKS controller repo'
        ]
      },
      {
        name: 'Kubernetes Gateway API',
        url: 'https://gateway-api.sigs.k8s.io/',
        prompts: [
          'Fix error: {error_message}',
          'Best practices for {resource}'
        ]
      }
    ];
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. It mentions that the tool lists sources with URLs and sample prompts, which implies a read-only operation, but doesn't specify if this requires authentication, how data is returned (e.g., pagination, format), or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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: 'List all available sources with their URLs and sample prompts.' It is front-loaded with the core action and includes no unnecessary words, making it highly concise and well-structured.

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 that there are no parameters and no output schema, the description provides a clear purpose but lacks details on behavioral aspects like authentication, return format, or error handling. For a simple list tool, this might be adequate, but without annotations or output schema, it doesn't fully prepare an agent for invocation, leaving room for improvement in completeness.

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, meaning there are no parameters to document. The description doesn't need to add parameter details, so it appropriately focuses on the tool's purpose. A baseline of 4 is applied since no parameters exist, and the description doesn't attempt to explain non-existent inputs.

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: 'List all available sources with their URLs and sample prompts.' It specifies the verb ('List'), resource ('available sources'), and what information is included ('URLs and sample prompts'). However, it doesn't explicitly distinguish this from sibling tools like 'get_source_prompts' or 'list_amazon_vpc_lattice_prompts', which might have overlapping functionality.

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. With sibling tools like 'get_source_prompts' and 'list_amazon_vpc_lattice_prompts' available, there is no indication of when this tool is appropriate, what prerequisites might be needed, or any exclusions for its use.

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