Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_bridge_list

Retrieve available bridge configurations from Sakura Cloud infrastructure to manage network connectivity and resource linking.

Instructions

Get list of bridges

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_bridge_list' tool. Validates credentials, calls fetchFromSakuraCloud('/bridge') to retrieve the list of bridges from Sakura Cloud API, formats the response as JSON text, and returns it.
    } else if (request.params.name === 'get_bridge_list') {
      try {
        validateCredentials();
        
        const bridgeList = await fetchFromSakuraCloud(`/bridge`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(bridgeList, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
    } else if (request.params.name === 'get_bridge_info') {
  • src/server.ts:908-916 (registration)
    Tool registration entry in ListToolsRequestSchema handler, defining the name, description, and empty input schema for 'get_bridge_list'.
    {
      name: 'get_bridge_list',
      description: 'Get list of bridges',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Inline input schema definition for the 'get_bridge_list' tool (accepts no parameters).
    {
      name: 'get_bridge_list',
      description: 'Get list of bridges',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Shared helper function fetchFromSakuraCloud used by the tool to make authenticated HTTPS GET request to Sakura Cloud API endpoint '/bridge'.
    async function fetchFromSakuraCloud(path: string, isPublicAPI: boolean = false, zone: string = DEFAULT_ZONE, method: string = 'GET', bodyData?: any): Promise<any> {
      return new Promise((resolve, reject) => {
        const basePath = isPublicAPI ? '/cloud/api/cloud/1.1' : `/cloud/zone/${zone}/api/cloud/1.1`;
        
        const options = {
          hostname: 'secure.sakura.ad.jp',
          port: 443,
          path: `${basePath}${path}`,
          method: method,
          headers: {
            'Accept': 'application/json',
            'Authorization': '',
            'Content-Type': 'application/json'
          }
        };
        
        // Add authorization for non-public APIs
        if (!isPublicAPI) {
          options.headers['Authorization'] = `Basic ${Buffer.from(`${SACLOUD_API_TOKEN}:${SACLOUD_API_SECRET}`).toString('base64')}`;
        }
    
        const req = https.request(options, (res) => {
          let data = '';
          
          res.on('data', (chunk) => {
            data += chunk;
          });
          
          res.on('end', () => {
            try {
              if (data) {
                const parsedData = JSON.parse(data);
                resolve(parsedData);
              } else {
                resolve({});
              }
            } catch (err) {
              reject(new Error(`Failed to parse response: ${err}`));
            }
          });
        });
        
        req.on('error', (error) => {
          reject(error);
        });
        
        if (bodyData && (method === 'POST' || method === 'PUT')) {
          req.write(JSON.stringify(bodyData));
        }
        
        req.end();
      });
    }
  • Helper function validateCredentials called by the tool handler to ensure API token and secret are set.
    function validateCredentials(): void {
      if (!SACLOUD_API_TOKEN || !SACLOUD_API_SECRET) {
        throw new Error('Missing API credentials. Set SACLOUD_API_TOKEN and SACLOUD_API_SECRET environment variables.');
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states a read operation ('Get'), implying it's likely safe and non-destructive, but doesn't specify aspects like pagination, sorting, filtering, rate limits, or authentication needs. For a list tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Get list of bridges') with no wasted words, making it front-loaded and easy to parse. However, it might be overly terse, potentially under-specifying the tool's scope or behavior, which slightly reduces its effectiveness.

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 for a list tool. It doesn't explain what the list contains (e.g., bridge IDs, names, statuses), how results are formatted, or any behavioral traits like limits or errors. With no structured data to rely on, the description should provide more context to be fully helpful.

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 no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none to explain. A baseline of 4 is applied as the description doesn't need to compensate for missing parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get list of bridges' clearly states the verb ('Get') and resource ('bridges'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_bridge_info' or other 'get_*_list' tools, leaving ambiguity about what distinguishes this specific list operation from others.

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 siblings like 'get_bridge_info' (likely for individual bridge details) and other list tools (e.g., 'get_server_list'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer 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/hidenorigoto/sacloud-mcp'

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