Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_zone_list

Retrieve available zones for infrastructure deployment and management in Sakura Cloud.

Instructions

Get list of zones

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_zone_list' tool in the ListTools response, including its name, description, and empty input schema.
      name: 'get_zone_list',
      description: 'Get list of zones',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Input schema for get_zone_list tool: an empty object (no parameters required).
        type: 'object',
        properties: {
        },
      }
    },
  • The handler implementation for the get_zone_list tool within the CallToolRequestSchema handler. It validates credentials, fetches the zone list from the Sakura Cloud API endpoint '/zone' using the fetchFromSakuraCloud helper, and returns the JSON stringified response.
    } else if (request.params.name === 'get_zone_list') {
      try {
        validateCredentials();
        
        const zoneList = await fetchFromSakuraCloud(`/zone`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(zoneList, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Shared helper function fetchFromSakuraCloud used by the get_zone_list handler to make authenticated HTTPS requests to the Sakura Cloud API. Called with path '/zone' to retrieve the list of zones.
    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. It states the action ('Get list') but doesn't describe what the list includes (e.g., zone names, IDs, statuses), whether it's paginated, requires authentication, or has rate limits. For a read operation 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.

Conciseness5/5

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

The description is extremely concise with just three words: 'Get list of zones'. It's front-loaded and wastes no words, making it easy to parse quickly. Every word earns its place by specifying the action and resource.

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 tool's simplicity (0 parameters, no output schema), the description is minimal but incomplete. It lacks details on what the list contains, how it's formatted, or any behavioral traits. With no annotations and no output schema, the description should provide more context about the return value and usage 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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain any parameters, so it appropriately avoids redundancy. A baseline of 4 is justified as the description doesn't add param info but doesn't need to compensate for any gaps.

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 zones' clearly states the verb ('Get') and resource ('zones'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_zone_info' (which presumably retrieves details about a specific zone rather than listing all zones), leaving room for ambiguity. It's not vague, but lacks sibling differentiation.

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. Given the sibling tool 'get_zone_info', there's a clear need to differentiate between listing zones and getting detailed information about a specific zone, but this is not addressed. No context or exclusions are mentioned.

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