Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

get_apprun_info

Retrieve detailed information about AppRun applications in Sakura Cloud, including configuration and status, by specifying the application ID and zone.

Instructions

Get detailed information about a specific AppRun application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe ID of the AppRun application to retrieve
zoneNoThe zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.

Implementation Reference

  • Handler function that executes the get_apprun_info tool by calling the AppRun API to fetch specific application details.
    } else if (request.params.name === 'get_apprun_info') {
      try {
        validateCredentials();
        
        const appId = request.params.arguments?.appId as string;
        if (!appId) {
          throw new Error('AppRun application ID is required');
        }
        
        const zone = request.params.arguments?.zone as string || DEFAULT_ZONE;
        const appRunInfo = await fetchFromAppRunAPI(`/applications/${appId}`);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(appRunInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Input schema definition and description for the get_apprun_info tool, registered in the ListTools response.
      name: 'get_apprun_info',
      description: 'Get detailed information about a specific AppRun application',
      inputSchema: {
        type: 'object',
        properties: {
          appId: {
            type: 'string',
            description: 'The ID of the AppRun application to retrieve'
          },
          zone: {
            type: 'string',
            description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
          }
        },
        required: ['appId']
      }
    },
  • Helper function fetchFromAppRunAPI used by the get_apprun_info handler to make authenticated API calls to Sakura Cloud AppRun service.
    async function fetchFromAppRunAPI(path: string, method: string = 'GET', bodyData?: any): Promise<any> {
      return new Promise((resolve, reject) => {
        validateCredentials();
        
        const options = {
          hostname: 'secure.sakura.ad.jp',
          port: 443,
          path: `/cloud/api/apprun/1.0/apprun/api${path}`,
          method: method,
          headers: {
            'Accept': 'application/json',
            'Content-Type': 'application/json',
            '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 full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation (implied by 'get'), authentication requirements, rate limits, error conditions, or what 'detailed information' includes. The agent must infer behavior from the name alone.

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 with zero waste. It front-loads the core purpose ('Get detailed information') and specifies the resource precisely. No extraneous words or redundant information detract from clarity.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' entails (e.g., status, configuration, metrics), potential side effects, or error handling. Given the complexity of application data, more context is needed for effective 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?

Schema description coverage is 100%, so the schema fully documents both parameters (appId and zone). The description adds no parameter-specific details beyond what's in the schema, such as example appId formats or zone implications. Baseline 3 is appropriate when 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 detailed information') and resource ('about a specific AppRun application'), making the purpose unambiguous. It distinguishes from siblings like 'get_apprun_list' (which lists multiple applications) and 'get_appliance_info' (which targets different resources), though it doesn't explicitly mention these distinctions.

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 doesn't mention prerequisites (e.g., needing an existing appId), contrast with 'get_apprun_list' for browsing, or specify use cases like troubleshooting or status checks. Usage is implied but not articulated.

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