Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_zone_info

Retrieve detailed zone information from Sakura Cloud infrastructure using the zone ID to manage cloud resources effectively.

Instructions

Get detailed information about a specific zone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneIdYesThe ID of the zone to retrieve

Implementation Reference

  • Handler implementation for the 'get_zone_info' tool. Extracts zoneId from arguments, calls fetchFromSakuraCloud('/zone/${zoneId}'), and returns JSON response.
    } else if (request.params.name === 'get_zone_info') {
      try {
        validateCredentials();
        
        const zoneId = request.params.arguments?.zoneId as string;
        if (!zoneId) {
          throw new Error('Zone ID is required');
        }
        
        const zoneInfo = await fetchFromSakuraCloud(`/zone/${zoneId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(zoneInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Tool registration in ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'get_zone_info',
      description: 'Get detailed information about a specific zone',
      inputSchema: {
        type: 'object',
        properties: {
          zoneId: {
            type: 'string',
            description: 'The ID of the zone to retrieve'
          }
        },
        required: ['zoneId']
      }
    },
  • Input schema definition for the 'get_zone_info' tool.
    {
      name: 'get_zone_info',
      description: 'Get detailed information about a specific zone',
      inputSchema: {
        type: 'object',
        properties: {
          zoneId: {
            type: 'string',
            description: 'The ID of the zone to retrieve'
          }
        },
        required: ['zoneId']
      }
    },
  • Core helper function used by get_zone_info tool to fetch data from Sakura Cloud API endpoint `/zone/${zoneId}`.
    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 called by the tool handler to validate API credentials before making requests.
    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 the full burden. It states it retrieves 'detailed information' but doesn't disclose behavioral traits such as whether it's a read-only operation, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps for an agent to understand how to use it effectively.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary details.

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, and the tool's role in a complex server with many siblings, the description is incomplete. It doesn't explain what 'detailed information' includes, how it differs from other info tools, or any behavioral aspects, leaving the agent with insufficient context for reliable use.

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%, with the parameter 'zoneId' clearly documented in the schema. The description adds no additional meaning beyond implying retrieval for a 'specific zone', which aligns with the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 zone'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_zone_list' or other 'get_*_info' tools, which would require mentioning what makes zone information unique or how it differs from other info-retrieval tools.

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. With siblings like 'get_zone_list' and many other 'get_*_info' tools, the description lacks context on prerequisites (e.g., needing a zone ID) or comparisons (e.g., use this for a single zone vs. 'get_zone_list' for multiple zones).

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