Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_archive_list

Retrieve available system images and templates for deploying servers and applications on Sakura Cloud infrastructure.

Instructions

Get list of archives

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_archive_list' tool within the CallToolRequestSchema. Fetches archive list from Sakura Cloud API using the fetchFromSakuraCloud helper, optionally using a specified zone, and returns JSON stringified response.
    } else if (request.params.name === 'get_archive_list') {
      try {
        validateCredentials();
        
        const zone = request.params.arguments?.zone as string || DEFAULT_ZONE;
        const archiveList = await fetchFromSakuraCloud(`/archive`, false, zone);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(archiveList, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • src/server.ts:863-870 (registration)
    Registration of the 'get_archive_list' tool in the ListToolsRequestSchema handler, including its description and empty input schema (no required parameters).
      name: 'get_archive_list',
      description: 'Get list of archives',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Input schema definition for the 'get_archive_list' tool: an empty object schema allowing optional 'zone' parameter (handled in handler).
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Core helper function used by the get_archive_list handler to make authenticated API calls to Sakura Cloud's archive endpoint.
    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. 'Get list of archives' implies a read-only operation, but it doesn't specify permissions required, pagination behavior, rate limits, or what the output looks like (e.g., format, fields). For a tool 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 'Get list of archives' is extremely concise—just three words—with zero wasted language. It's front-loaded and to the point, making it efficient for an AI agent to parse, though this brevity contributes to gaps in other dimensions.

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 complexity (a list operation with no parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'archives' entails, the return format, or any behavioral aspects like sorting or filtering. For a tool in a server with many siblings, more context is needed to ensure correct usage.

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 input schema has 0 parameters with 100% coverage, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it doesn't introduce confusion or redundancy regarding parameters.

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 archives' clearly states the verb ('Get') and resource ('archives'), making the basic purpose understandable. However, it doesn't differentiate from sibling tools like 'get_archive_info' or specify what type of archives (e.g., backup archives, data archives) or what context (e.g., system, user) is involved, leaving it somewhat vague.

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 siblings like 'get_archive_info' (likely for details of a specific archive) and other list tools (e.g., 'get_apprun_list'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on naming alone.

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