Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_cdrom_info

Retrieve detailed information about a specific ISO image in Sakura Cloud infrastructure by providing its ID.

Instructions

Get detailed information about a specific ISO image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cdromIdYesThe ID of the ISO image to retrieve

Implementation Reference

  • The handler logic for the 'get_cdrom_info' tool within the CallToolRequestSchema handler. It validates credentials, extracts the cdromId from arguments, calls the Sakura Cloud API to fetch specific CDROM info, and returns the JSON response.
    } else if (request.params.name === 'get_cdrom_info') {
      try {
        validateCredentials();
        
        const cdromId = request.params.arguments?.cdromId as string;
        if (!cdromId) {
          throw new Error('ISO Image ID is required');
        }
        
        const cdromInfo = await fetchFromSakuraCloud(`/cdrom/${cdromId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(cdromInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • src/server.ts:896-907 (registration)
    Registration of the 'get_cdrom_info' tool in the ListToolsRequestSchema response, including name, description, and input schema definition.
      description: 'Get detailed information about a specific ISO image',
      inputSchema: {
        type: 'object',
        properties: {
          cdromId: {
            type: 'string',
            description: 'The ID of the ISO image to retrieve'
          }
        },
        required: ['cdromId']
      }
    },
  • Input schema definition for the 'get_cdrom_info' tool, specifying the required cdromId parameter.
        type: 'object',
        properties: {
          cdromId: {
            type: 'string',
            description: 'The ID of the ISO image to retrieve'
          }
        },
        required: ['cdromId']
      }
    },
  • Core helper function fetchFromSakuraCloud used by the get_cdrom_info handler to make authenticated HTTPS requests to the Sakura Cloud API endpoint `/cdrom/{cdromId}`.
    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 handler to ensure API credentials are set before making requests.
    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 the full burden. It states this is a read operation ('Get'), but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or what 'detailed information' includes (e.g., metadata, size, status). For a tool with zero annotation coverage, this is a significant gap.

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 front-loads the core action ('Get detailed information') without any wasted words. It's appropriately sized for a simple lookup tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter, read-only implied), 100% schema coverage, but no annotations or output schema, the description is minimally adequate. It states the purpose clearly but lacks behavioral details and usage context, leaving gaps for an agent to infer correct invocation.

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 parameter 'cdromId' clearly documented in the schema as 'The ID of the ISO image to retrieve'. The description adds no additional meaning beyond implying specificity ('specific ISO image'), so it meets the baseline of 3 where the schema does the heavy lifting.

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 ISO image'), making the purpose unambiguous. However, it doesn't explicitly differentiate from its sibling 'get_cdrom_list' (which presumably lists multiple ISO images) beyond implying specificity through 'specific ISO image'.

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 like 'get_cdrom_list' or other 'get_*_info' tools. It lacks context about prerequisites, such as needing the ISO ID from a list operation, or any exclusions.

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