Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_product_info

Retrieve detailed specifications and configuration options for Sakura Cloud products including servers, disks, internet services, and licenses to inform infrastructure decisions.

Instructions

Get detailed information about specific product offerings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productTypeYesThe type of product to retrieve (server, disk, internet, license)

Implementation Reference

  • Executes the get_product_info tool: validates productType (server/disk/internet/license), calls Sakura Cloud API via fetchFromSakuraCloud, returns JSON response.
    } else if (request.params.name === 'get_product_info') {
      try {
        validateCredentials();
        
        const productType = request.params.arguments?.productType as string;
        if (!productType) {
          throw new Error('Product type is required');
        }
        
        // Validate product type
        if (!['server', 'disk', 'internet', 'license'].includes(productType)) {
          throw new Error('Invalid product type. Must be one of: server, disk, internet, license');
        }
        
        const productInfo = await fetchFromSakuraCloud(`/product/${productType}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(productInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Registers the get_product_info tool in ListToolsRequestSchema handler with description and input schema definition.
      name: 'get_product_info',
      description: 'Get detailed information about specific product offerings',
      inputSchema: {
        type: 'object',
        properties: {
          productType: {
            type: 'string',
            description: 'The type of product to retrieve (server, disk, internet, license)',
            enum: ['server', 'disk', 'internet', 'license']
          }
        },
        required: ['productType']
      }
    },
  • Core helper function fetchFromSakuraCloud that performs HTTPS requests to Sakura Cloud API endpoints, handles authentication, used directly by the tool handler.
    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();
      });
    }
  • Validates presence of Sakura Cloud API credentials before making requests, called by the tool handler.
    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 full burden for behavioral disclosure. While 'Get detailed information' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what format the information will be returned in. 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.

Conciseness5/5

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

The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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, plus the existence of many similar-looking sibling tools, the description is insufficiently complete. It doesn't clarify the relationship to other 'get_*_info' tools, doesn't describe the return format, and provides minimal behavioral context for a tool that presumably queries product data.

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 single parameter 'productType' fully documented including its enum values. The description doesn't add any parameter semantics beyond what the schema already provides, so it meets the baseline score of 3 for high schema coverage.

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 action ('Get detailed information') and resource ('specific product offerings'), making the purpose understandable. However, it doesn't differentiate this tool from its many sibling 'get_*_info' tools (like get_server_info, get_disk_info, etc.), which appear to serve similar purposes for specific product types.

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 numerous sibling tools like get_server_info, get_disk_info, and get_license_info that appear to retrieve information about specific product types, there's no indication whether this tool is a general-purpose alternative, a superset, or serves a different scope.

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