Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_region_info

Retrieve detailed infrastructure information for a specific region in Sakura Cloud to manage servers, disks, networks, and containerized applications.

Instructions

Get detailed information about a specific region

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdYesThe ID of the region to retrieve

Implementation Reference

  • The handler logic for the get_region_info tool. Validates credentials, extracts the regionId from input arguments, calls the Sakura Cloud API to fetch region details, and returns the JSON-formatted response.
    } else if (request.params.name === 'get_region_info') {
      try {
        validateCredentials();
        
        const regionId = request.params.arguments?.regionId as string;
        if (!regionId) {
          throw new Error('Region ID is required');
        }
        
        const regionInfo = await fetchFromSakuraCloud(`/region/${regionId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(regionInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Registration of the get_region_info tool in the ListToolsRequestSchema response, including its description and input schema requiring a regionId.
      name: 'get_region_info',
      description: 'Get detailed information about a specific region',
      inputSchema: {
        type: 'object',
        properties: {
          regionId: {
            type: 'string',
            description: 'The ID of the region to retrieve'
          }
        },
        required: ['regionId']
      }
    },
  • Input schema definition for the get_region_info tool, specifying an object with a required string regionId.
    inputSchema: {
      type: 'object',
      properties: {
        regionId: {
          type: 'string',
          description: 'The ID of the region to retrieve'
        }
      },
      required: ['regionId']
    }
  • Shared helper function fetchFromSakuraCloud used by the get_region_info handler to perform the actual API request to retrieve region information.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description doesn't mention authentication requirements, rate limits, error conditions, or what format the detailed information will be returned in. For a tool with no annotation coverage, this is insufficient behavioral context.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a simple read operation with one well-documented parameter and no output schema, the description is minimally adequate. However, it doesn't explain what constitutes 'detailed information' or provide any context about the data structure returned, which would be helpful given the absence of an output schema.

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 input schema has 100% description coverage, with the single parameter 'regionId' clearly documented. The description doesn't add any additional parameter semantics beyond what's already in the schema, so it meets the baseline score of 3 for high schema coverage situations.

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 the resource 'detailed information about a specific region', making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_region_list' which presumably lists regions rather than providing detailed information about one specific region.

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_region_list' available, there's no indication of when to retrieve detailed information about a single region versus listing all regions, nor any mention of prerequisites or typical use cases.

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