Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_archive_info

Retrieve detailed information about a specific archive in Sakura Cloud infrastructure using its unique archive ID.

Instructions

Get detailed information about a specific archive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
archiveIdYesThe ID of the archive to retrieve

Implementation Reference

  • Handler implementation for the 'get_archive_info' tool within the CallToolRequestSchema request handler. Validates input, fetches archive details from Sakura Cloud API using the helper function, and returns JSON response.
    } else if (request.params.name === 'get_archive_info') {
      try {
        validateCredentials();
        
        const archiveId = request.params.arguments?.archiveId as string;
        if (!archiveId) {
          throw new Error('Archive ID is required');
        }
        
        const zone = request.params.arguments?.zone as string || DEFAULT_ZONE;
        const archiveInfo = await fetchFromSakuraCloud(`/archive/${archiveId}`, false, zone);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(archiveInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • src/server.ts:872-884 (registration)
    Tool registration entry in the ListToolsRequestSchema handler, including name, description, and input schema definition.
      name: 'get_archive_info',
      description: 'Get detailed information about a specific archive',
      inputSchema: {
        type: 'object',
        properties: {
          archiveId: {
            type: 'string',
            description: 'The ID of the archive to retrieve'
          }
        },
        required: ['archiveId']
      }
    },
  • Reusable helper function to make authenticated HTTPS requests to the Sakura Cloud API, used by the get_archive_info handler to retrieve archive 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. It states the tool retrieves information, implying a read-only operation, but does not cover aspects like authentication requirements, rate limits, error handling, or the format of returned data. This is a significant gap for a tool with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an AI agent to parse quickly.

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, the description is incomplete. It does not explain what 'detailed information' includes, how the data is structured, or potential behavioral traits like side effects. For a tool that retrieves specific entity details, more context is needed to guide effective usage.

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 'archiveId' parameter clearly documented. The description adds no additional meaning beyond the schema, such as explaining what an archive ID is or where to find it. Given the high schema coverage, a baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 archive'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'get_archive_list' (which likely lists archives rather than retrieving details for one), leaving room for improvement in sibling distinction.

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. For example, it does not mention when to use 'get_archive_info' over 'get_archive_list' or other 'get_*_info' tools, nor does it specify prerequisites like needing an archive ID. This lack of context reduces its utility for an AI agent.

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