Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_privatehost_info

Retrieve detailed configuration and status information for a specific private host in Sakura Cloud infrastructure management.

Instructions

Get detailed information about a specific private host

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privateHostIdYesThe ID of the private host to retrieve

Implementation Reference

  • Executes the get_privatehost_info tool: validates credentials, fetches specific private host details from Sakura Cloud API using fetchFromSakuraCloud('/privatehost/{id}'), and returns JSON response.
    } else if (request.params.name === 'get_privatehost_info') {
      try {
        validateCredentials();
        
        const privateHostId = request.params.arguments?.privateHostId as string;
        if (!privateHostId) {
          throw new Error('Private Host ID is required');
        }
        
        const privateHostInfo = await fetchFromSakuraCloud(`/privatehost/${privateHostId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(privateHostInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
    } else if (request.params.name === 'get_public_price') {
  • Registers the get_privatehost_info tool in the ListTools response, providing name, description, and input schema requiring privateHostId.
      name: 'get_privatehost_info',
      description: 'Get detailed information about a specific private host',
      inputSchema: {
        type: 'object',
        properties: {
          privateHostId: {
            type: 'string',
            description: 'The ID of the private host to retrieve'
          }
        },
        required: ['privateHostId']
      }
    },
  • Input schema definition for get_privatehost_info tool: object with required string privateHostId.
      type: 'object',
      properties: {
        privateHostId: {
          type: 'string',
          description: 'The ID of the private host to retrieve'
        }
      },
      required: ['privateHostId']
    }
  • Core helper function fetchFromSakuraCloud that makes authenticated HTTPS requests to Sakura Cloud API endpoints, used 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();
      });
    }
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 the tool retrieves information, implying a read-only operation, but does not disclose behavioral traits like authentication requirements, rate limits, error conditions, or what 'detailed information' includes (e.g., format, fields). This leaves significant gaps for an agent.

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 is front-loaded with the core purpose. There is no wasted wording, making it easy for an 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' entails (e.g., JSON structure, key fields) or address potential complexities like error handling. For a tool with no structured support, more context is needed.

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 parameter 'privateHostId' clearly documented. The description adds no additional meaning beyond the schema, such as examples or constraints (e.g., ID format). Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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 the resource 'detailed information about a specific private host', which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_server_info' or 'get_appliance_info', which follow similar patterns for different resources.

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. It lacks context such as prerequisites (e.g., needing a valid private host ID) or comparisons to sibling tools like 'get_privatehost_list' (if it existed) for listing versus retrieving details.

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