Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_appliance_list

Retrieve available appliance configurations from Sakura Cloud infrastructure to manage server resources and deployment options.

Instructions

Get list of appliances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneNoThe zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.

Implementation Reference

  • The handler logic for the 'get_appliance_list' tool. Validates credentials, fetches the appliance list from the Sakura Cloud API using the helper function with optional zone parameter, and returns the JSON-formatted result.
    } else if (request.params.name === 'get_appliance_list') {
      try {
        validateCredentials();
        
        const zone = request.params.arguments?.zone as string || DEFAULT_ZONE;
        const applianceList = await fetchFromSakuraCloud(`/appliance`, false, zone);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(applianceList, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • src/server.ts:804-816 (registration)
    Registration of the 'get_appliance_list' tool in the ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'get_appliance_list',
      description: 'Get list of appliances',
      inputSchema: {
        type: 'object',
        properties: {
          zone: {
            type: 'string',
            description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
          }
        },
      }
    },
  • Input schema definition for the 'get_appliance_list' tool, allowing optional 'zone' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        zone: {
          type: 'string',
          description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
        }
      },
    }
  • Core helper function fetchFromSakuraCloud used by the tool handler to make authenticated HTTPS requests to the Sakura Cloud API, specifically called with path '/appliance' for this tool.
    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 the tool handler to ensure API tokens are set 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 of behavioral disclosure. It only states the action ('Get list') without mentioning whether this is a read-only operation, if it requires authentication, what the output format might be (e.g., list of names vs. full objects), or any rate limits. For a tool with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is extremely concise at three words, which is efficient for a simple tool. However, it's arguably too brief given the lack of sibling differentiation and behavioral context—every word earns its place, but more words might be warranted to improve clarity. It's front-loaded but under-specified.

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 (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'appliances' refers to in this context (e.g., virtual machines, devices), what the list contains, or how it relates to sibling tools. For a tool in a server with many similar 'get_' tools, more context is needed to avoid confusion.

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 'zone' parameter fully documented in the schema itself (including default value and examples). The description adds no additional parameter information beyond what's in the schema. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't need to compensate but also adds no extra value.

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 appliances' clearly states the verb ('Get') and resource ('appliances'), making the basic purpose understandable. However, it doesn't differentiate this tool from similar sibling tools like 'get_appliance_info' or 'get_apprun_list', leaving ambiguity about what specific aspect of appliances it retrieves. The purpose is clear 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. With sibling tools like 'get_appliance_info' (likely for detailed info on a specific appliance) and 'get_apprun_list' (likely for appliance runs), there's no indication of whether this tool returns basic metadata, full details, or something else. 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