Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_sshkey_info

Retrieve detailed information about a specific SSH key in Sakura Cloud infrastructure to manage access and configuration.

Instructions

Get detailed information about a specific SSH key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sshkeyIdYesThe ID of the SSH key to retrieve

Implementation Reference

  • The execution handler for the 'get_sshkey_info' tool. It validates credentials, extracts the sshkeyId from arguments, calls the Sakura Cloud API via fetchFromSakuraCloud to retrieve the SSH key details, and returns the JSON stringified response.
    } else if (request.params.name === 'get_sshkey_info') {
      try {
        validateCredentials();
        
        const sshkeyId = request.params.arguments?.sshkeyId as string;
        if (!sshkeyId) {
          throw new Error('SSH Key ID is required');
        }
        
        const sshkeyInfo = await fetchFromSakuraCloud(`/sshkey/${sshkeyId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(sshkeyInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Registration of the 'get_sshkey_info' tool in the ListToolsRequestSchema handler, including its name, description, and input schema definition.
    {
      name: 'get_sshkey_info',
      description: 'Get detailed information about a specific SSH key',
      inputSchema: {
        type: 'object',
        properties: {
          sshkeyId: {
            type: 'string',
            description: 'The ID of the SSH key to retrieve'
          }
        },
        required: ['sshkeyId']
      }
    },
  • Helper function fetchFromSakuraCloud used by the get_sshkey_info handler to make authenticated HTTPS requests to the Sakura Cloud API endpoint `/sshkey/{sshkeyId}`.
    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.
    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 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 constitutes 'detailed information' (format, fields included). This leaves significant behavioral gaps for a tool with no annotation coverage.

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 gets straight to the point with zero wasted 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.

Completeness3/5

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

For a simple read operation with one well-documented parameter and no output schema, the description is minimally adequate. However, without annotations or output schema, it should ideally provide more context about what information is returned, authentication needs, or error handling to be fully complete.

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 has 100% description coverage, with the single parameter 'sshkeyId' clearly documented as 'The ID of the SSH key to retrieve.' The description adds no additional parameter semantics beyond what the schema already provides, which meets the baseline expectation when schema coverage is high.

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 target resource ('about a specific SSH key'), which is a specific verb+resource combination. However, it doesn't distinguish this from its sibling 'get_sshkey_list' which presumably lists SSH keys rather than retrieving details about 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?

The description provides no guidance on when to use this tool versus alternatives like 'get_sshkey_list' or other information-retrieval tools. It doesn't mention prerequisites, appropriate contexts, or exclusions for usage.

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