Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_icon_info

Retrieve detailed information about a specific icon by providing its ID, enabling users to access icon metadata and properties within Sakura Cloud infrastructure management.

Instructions

Get detailed information about a specific icon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconIdYesThe ID of the icon to retrieve

Implementation Reference

  • The handler implementation for the 'get_icon_info' tool. It validates credentials, extracts the iconId from arguments, fetches the icon information from Sakura Cloud API endpoint `/icon/{iconId}`, and returns the JSON stringified response.
    } else if (request.params.name === 'get_icon_info') {
      try {
        validateCredentials();
        
        const iconId = request.params.arguments?.iconId as string;
        if (!iconId) {
          throw new Error('Icon ID is required');
        }
        
        const iconInfo = await fetchFromSakuraCloud(`/icon/${iconId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(iconInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • src/server.ts:987-998 (registration)
    Registration of the 'get_icon_info' tool in the listTools response, including its description and input schema requiring an 'iconId' string.
    name: 'get_icon_info',
    description: 'Get detailed information about a specific icon',
    inputSchema: {
      type: 'object',
      properties: {
        iconId: {
          type: 'string',
          description: 'The ID of the icon to retrieve'
        }
      },
      required: ['iconId']
    }
  • Helper function fetchFromSakuraCloud used by the get_icon_info handler to make authenticated HTTPS requests to the Sakura Cloud API.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but does not cover aspects like authentication requirements, rate limits, error handling, or the format of the returned information. This leaves significant gaps for a tool that likely interacts with a system resource.

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, clear sentence with no wasted words. It is front-loaded with the core action ('Get detailed information'), making it efficient and easy to parse.

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 insufficient for a tool that retrieves system resource information. It does not explain what 'detailed information' includes, potential side effects, or error conditions, leaving the agent with incomplete context for reliable 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 input schema has 100% description coverage, with the 'iconId' parameter clearly documented. The description adds no additional semantic context beyond implying retrieval of details for a specific icon, which aligns with the schema. This meets the baseline for high schema coverage.

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 icon'), making the purpose understandable. However, it does not differentiate this tool from its sibling 'get_icon_list' (which presumably lists icons rather than retrieving details for a specific one), preventing a perfect score.

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_icon_list' or other 'get_*_info' tools. It lacks context about prerequisites (e.g., needing an icon ID) or exclusions, offering only a basic statement of function.

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