Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_switch_info

Retrieve detailed configuration and status information for a specific network switch in Sakura Cloud infrastructure to manage network resources effectively.

Instructions

Get detailed information about a specific switch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
switchIdYesThe ID of the switch to retrieve
zoneNoThe zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.

Implementation Reference

  • The main handler function for the 'get_switch_info' tool. It validates credentials, extracts switchId and optional zone from arguments, calls the Sakura Cloud API to fetch switch details, and returns the JSON response.
    } else if (request.params.name === 'get_switch_info') {
      try {
        validateCredentials();
        
        const switchId = request.params.arguments?.switchId as string;
        if (!switchId) {
          throw new Error('Switch ID is required');
        }
        
        const zone = request.params.arguments?.zone as string || DEFAULT_ZONE;
        const switchInfo = await fetchFromSakuraCloud(`/switch/${switchId}`, false, zone);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(switchInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • The tool registration entry in ListToolsRequestSchema handler, including name, description, and input schema definition for get_switch_info.
    name: 'get_switch_info',
    description: 'Get detailed information about a specific switch',
    inputSchema: {
      type: 'object',
      properties: {
        switchId: {
          type: 'string',
          description: 'The ID of the switch to retrieve'
        },
        zone: {
          type: 'string',
          description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
        }
      },
      required: ['switchId']
    }
  • Core helper function fetchFromSakuraCloud used by the tool handler to make authenticated HTTPS requests to the Sakura Cloud API endpoints.
    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();
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it retrieves 'detailed information' but doesn't specify what that includes, whether it's a read-only operation, potential errors, or any rate limits. This leaves significant gaps for a tool that likely interacts with network infrastructure.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

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 insufficient. It doesn't explain what 'detailed information' includes, potential error conditions, or how this tool differs from siblings in a server with 40+ tools. For a network resource tool, more context is needed.

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 fully documents both parameters (switchId and zone). The description adds no additional parameter semantics beyond implying retrieval for a 'specific switch', which aligns with the schema. This meets the baseline for high schema coverage.

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 verb ('Get') and resource ('detailed information about a specific switch'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_switch_list' or 'get_bridge_info', which reduces its score from a perfect 5.

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_switch_list' for listing switches or 'get_bridge_info' for related network 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

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