Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_license_list

Retrieve available software licenses for managing Sakura Cloud infrastructure resources and applications.

Instructions

Get list of licenses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'get_license_list' tool. It validates credentials, fetches the license list from the Sakura Cloud API using the fetchFromSakuraCloud helper, and returns the result as a JSON text content block.
    } else if (request.params.name === 'get_license_list') {
      try {
        validateCredentials();
        
        const licenseList = await fetchFromSakuraCloud(`/license`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(licenseList, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Registration of the 'get_license_list' tool within the ListToolsRequestSchema handler. Defines the tool's name, description, and empty input schema.
      name: 'get_license_list',
      description: 'Get list of licenses',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Input schema definition for the 'get_license_list' tool (no required parameters).
      name: 'get_license_list',
      description: 'Get list of licenses',
      inputSchema: {
        type: 'object',
        properties: {
        },
      }
    },
  • Core helper function fetchFromSakuraCloud used by the get_license_list handler to make authenticated HTTPS requests to the Sakura Cloud API endpoint '/license'.
    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 get_license_list handler to ensure API credentials are set before making the API request.
    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. It states 'Get list' which implies a read operation, but doesn't disclose behavioral traits like whether it requires authentication, returns paginated results, has rate limits, or what format the list is in. For a tool with zero annotation coverage, this is insufficient 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 is extremely concise at three words ('Get list of licenses'), front-loaded with the core action, and has zero wasted text. Every word earns its place by specifying the verb and resource without unnecessary elaboration.

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 no annotations, no output schema, and a simple list operation, the description is incomplete. It doesn't explain what the list contains, how it's structured, or any behavioral context. For a tool in a server with many siblings, more completeness is needed to help the agent understand this tool's role and output.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, and it doesn't add or contradict any parameter information. Baseline is 4 for zero parameters as the description appropriately doesn't discuss nonexistent inputs.

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 licenses' clearly states the verb ('Get') and resource ('licenses'), but it's vague about scope and doesn't distinguish from sibling tools like 'get_license_info' which might retrieve details about a specific license. It provides basic purpose but lacks specificity about what kind of list (e.g., all licenses, filtered, paginated).

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 about when to use this tool versus alternatives like 'get_license_info' or other list tools. The description doesn't mention prerequisites, context, or exclusions. With many sibling tools present, this lack of differentiation leaves the agent without clear selection criteria.

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