Skip to main content
Glama
simplypixi

BugBug MCP Server

by simplypixi

get_ip_addresses

Retrieve BugBug infrastructure IP addresses for configuring firewall rules or network access controls.

Instructions

Get list of BugBug infrastructure IP addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_ip_addresses' tool. It calls the BugBug API client to fetch IP addresses, formats the response as a markdown list, and handles errors by returning structured content blocks.
    handler: async () => {
      try {
        const response = await bugbugClient.getIpAddresses();
        
        if (response.status !== 200) {
          return {
            content: [
              {
                type: 'text',
                text: `Error: ${response.status} ${response.statusText}`,
              },
            ],
          };
        }
    
        const ipList = response.data.map((ip: string) => `- ${ip}`).join('\n');
        
        return {
          content: [
            {
              type: 'text',
              text: `**BugBug Infrastructure IP Addresses:**\n\n${ipList}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching IP addresses: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
        };
      }
    }
  • Input schema for the 'get_ip_addresses' tool, defined as an empty object using Zod (no input parameters required).
    inputSchema: z.object({}).shape,
  • Registration of all tools on the MCP server, including 'get_ip_addresses' via spreading configTools (which exports getIpAddressesTool).
    export function registerAllTools(server: McpServer): void {
      const tools: Record<string, Tool> = {
        ...configTools,
        ...testsTools,
        ...testRunsTools,
        ...suitesTools,
        ...suiteRunsTools,
        ...profilesTools,
        ...advancedTools,
      };
    
      for (const t in tools) {
        server.registerTool(
          tools[t].name,
          {
            description: tools[t].description,
            inputSchema: tools[t].inputSchema,
            annotations: { title: tools[t].title },
          },
          (args: unknown) => tools[t].handler(args as unknown)
        );
      }
    }
  • Helper method in BugBugApiClient class that performs the actual API request to fetch the list of IP addresses from the '/config/ips/' endpoint.
    async getIpAddresses(): Promise<ApiResponse<string[]>> {
      return this.makeRequest<string[]>('/config/ips/');
    }
Behavior3/5

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

Annotations provide a title but no hints like readOnly or destructive. The description adds minimal behavioral context, stating it retrieves a list, but doesn't disclose details such as rate limits, authentication needs, or output format. With no annotations to contradict, it's adequate but sparse.

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 function without unnecessary words. It's front-loaded and wastes no space, 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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks details on output format or behavioral traits, which could be helpful for an agent despite the low complexity.

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 coverage, so no parameter documentation is needed. The description doesn't add param info, but this is acceptable given the lack of inputs, aligning with the baseline for zero parameters.

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 list') and resource ('BugBug infrastructure IP addresses'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_profile' or 'get_tests' beyond the resource type, missing explicit sibling 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, timing, or comparisons to sibling tools, offering only a basic statement of function without usage instructions.

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/simplypixi/bugbug-mcp-server'

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