Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

start_apprun

Start a containerized application on Sakura Cloud by providing the application ID and optional zone. Use this tool to launch AppRun applications for deployment or testing.

Instructions

Start an AppRun application

Input Schema

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

Implementation Reference

  • Handler for the 'start_apprun' tool. Extracts appId and optional zone from arguments, validates credentials, calls the AppRun API via POST to /applications/{appId}/start, and returns the result as JSON text.
    } else if (request.params.name === 'start_apprun') {
      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 startResult = await fetchFromAppRunAPI(`/applications/${appId}/start`, 'POST');
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(startResult, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Registration of the 'start_apprun' tool in the ListToolsRequestSchema handler, including name, description, and input schema definition.
      name: 'start_apprun',
      description: 'Start an AppRun application',
      inputSchema: {
        type: 'object',
        properties: {
          appId: {
            type: 'string',
            description: 'The ID of the AppRun application to start'
          },
          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 start_apprun handler to make authenticated HTTPS POST requests to the Sakura Cloud AppRun API.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Start') but doesn't describe what starting entails (e.g., booting a virtual machine, launching a service), potential side effects (e.g., resource consumption, billing implications), error conditions, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, direct sentence with zero wasted words. It front-loads the key action and resource, making it immediately understandable. Every part of the sentence earns its place by conveying the essential purpose without redundancy or fluff.

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 complexity of starting an application (a mutation operation), the lack of annotations and output schema, and the description's minimalism, it is incomplete. It doesn't cover behavioral aspects, error handling, or return values, which are critical for an agent to use the tool effectively. The high schema coverage for parameters doesn't compensate for these broader gaps.

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 clear documentation for both parameters ('appId' and 'zone'), including default values. The description adds no additional parameter semantics beyond what the schema provides, such as format examples for 'appId' or implications of zone selection. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles 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 action ('Start') and the resource ('an AppRun application'), which is specific and unambiguous. It distinguishes from sibling tools like 'stop_apprun' and 'create_apprun' by focusing on initiating an existing application. However, it doesn't explicitly differentiate from other tools that might involve application management, such as 'update_apprun', which slightly limits its clarity.

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., the application must exist and be stopped), contrast with 'stop_apprun' or 'update_apprun', or specify scenarios for usage. This lack of context leaves the agent to infer usage from the tool name alone.

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