Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_license_info

Retrieve detailed information about a specific Sakura Cloud license by providing its ID. This tool helps users access license specifications and manage infrastructure resources.

Instructions

Get detailed information about a specific license

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
licenseIdYesThe ID of the license to retrieve

Implementation Reference

  • Executes the get_license_info tool: validates credentials, retrieves license ID from arguments, calls fetchFromSakuraCloud to get details from /license/{licenseId} API endpoint, and returns JSON-formatted response.
      try {
        validateCredentials();
        
        const licenseId = request.params.arguments?.licenseId as string;
        if (!licenseId) {
          throw new Error('License ID is required');
        }
        
        const licenseInfo = await fetchFromSakuraCloud(`/license/${licenseId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(licenseInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
    } else if (request.params.name === 'get_bill_info') {
  • Registers the get_license_info tool in ListToolsRequestSchema handler, providing name, description, and input schema requiring licenseId.
    {
      name: 'get_license_info',
      description: 'Get detailed information about a specific license',
      inputSchema: {
        type: 'object',
        properties: {
          licenseId: {
            type: 'string',
            description: 'The ID of the license to retrieve'
          }
        },
        required: ['licenseId']
      }
    },
  • Input schema definition for get_license_info tool: object with required string licenseId.
    inputSchema: {
      type: 'object',
      properties: {
        licenseId: {
          type: 'string',
          description: 'The ID of the license to retrieve'
        }
      },
      required: ['licenseId']
    }
  • Shared helper function that makes authenticated HTTPS requests to Sakura Cloud API endpoints. Called by the handler with path `/license/${licenseId}` to fetch the license details.
    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 called by the handler to ensure Sakura Cloud API credentials are set in environment variables.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention any behavioral traits like authentication requirements, rate limits, error conditions, or what 'detailed information' includes. This leaves significant gaps for an agent to understand how to use it effectively.

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 any unnecessary words. It's appropriately sized and front-loaded, making it easy 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 insufficiently complete. It doesn't explain what 'detailed information' includes, how the licenseId should be formatted, or what the return structure looks like. For a tool with no structured output documentation, this leaves too many unknowns for effective use.

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 schema description coverage is 100%, with the single parameter 'licenseId' fully documented in the schema. The description doesn't add any additional meaning beyond what the schema provides about this parameter, so it meets the baseline score of 3 for adequate coverage without extra value.

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 license'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_license_list', which presumably lists multiple licenses rather than retrieving details for a specific one.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_license_list'. The description implies it's for retrieving details of a specific license, but there's no explicit comparison or context about when this is preferred over listing licenses.

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