Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_router_info

Retrieve detailed configuration and status information for a specific router in Sakura Cloud infrastructure to manage network settings and monitor performance.

Instructions

Get detailed information about a specific router

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routerIdYesThe ID of the router to retrieve

Implementation Reference

  • src/server.ts:941-952 (registration)
    Registration of the 'get_router_info' tool in the ListToolsRequestSchema handler, including its name, description, and input schema.
    name: 'get_router_info',
    description: 'Get detailed information about a specific router',
    inputSchema: {
      type: 'object',
      properties: {
        routerId: {
          type: 'string',
          description: 'The ID of the router to retrieve'
        }
      },
      required: ['routerId']
    }
  • Input schema definition for the get_router_info tool.
    inputSchema: {
      type: 'object',
      properties: {
        routerId: {
          type: 'string',
          description: 'The ID of the router to retrieve'
        }
      },
      required: ['routerId']
  • The main handler logic for executing the get_router_info tool within the CallToolRequestSchema handler. It validates credentials, extracts routerId from arguments, fetches data from Sakura Cloud API endpoint `/internet/${routerId}`, and returns the JSON response.
    } else if (request.params.name === 'get_router_info') {
      try {
        validateCredentials();
        
        const routerId = request.params.arguments?.routerId as string;
        if (!routerId) {
          throw new Error('Router ID is required');
        }
        
        const routerInfo = await fetchFromSakuraCloud(`/internet/${routerId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(routerInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Core helper function fetchFromSakuraCloud used by get_router_info to make HTTPS requests to Sakura Cloud API, handling authentication, JSON parsing, and errors.
    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 get_router_info handler to ensure API credentials 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?

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 (e.g., configuration, status, metrics), whether it's a read-only operation, potential errors, or response format. This leaves significant gaps for a tool with unknown behavioral traits.

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 front-loads the core action and resource. There is no wasted verbiage or unnecessary elaboration, making it highly concise and well-structured for quick comprehension.

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 insufficiently complete. It doesn't explain what 'detailed information' entails, potential return values, or behavioral aspects like error handling. For a tool with no structured context, more descriptive detail is needed to adequately inform usage.

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?

The schema description coverage is 100%, with the parameter 'routerId' fully documented in the schema. The description adds no additional parameter semantics beyond implying it targets a 'specific router', which aligns with the schema but doesn't provide extra value. 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 router'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_router_list' or 'get_appliance_info', which would require more specific scope or resource distinction for a perfect score.

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. It doesn't mention sibling tools like 'get_router_list' for listing routers or 'get_appliance_info' for other resources, nor does it specify prerequisites or contextual usage scenarios.

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