Skip to main content
Glama
hidenorigoto

Sakura Cloud MCP Server

by hidenorigoto

stop_apprun

Stop a running AppRun application in Sakura Cloud by specifying its application ID and optional zone to manage containerized applications.

Instructions

Stop an AppRun application

Input Schema

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

Implementation Reference

  • Handler implementation for the 'stop_apprun' tool. Extracts appId from arguments, optionally uses zone, calls the AppRun API to stop the application via POST /applications/{appId}/stop, and returns the result as JSON text content.
    } else if (request.params.name === 'stop_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 stopResult = await fetchFromAppRunAPI(`/applications/${appId}/stop`, 'POST');
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(stopResult, null, 2)
            }
          ]
        };
      } catch (error) {
        console.error('Error calling tool:', error);
        throw error;
      }
  • Tool registration entry in ListToolsRequestSchema response, defining the name, description, and input schema for 'stop_apprun'.
      name: 'stop_apprun',
      description: 'Stop an AppRun application',
      inputSchema: {
        type: 'object',
        properties: {
          appId: {
            type: 'string',
            description: 'The ID of the AppRun application to stop'
          },
          zone: {
            type: 'string',
            description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
          }
        },
        required: ['appId']
      }
    },
  • Input schema definition for the 'stop_apprun' tool, specifying required appId and optional zone parameters.
      inputSchema: {
        type: 'object',
        properties: {
          appId: {
            type: 'string',
            description: 'The ID of the AppRun application to stop'
          },
          zone: {
            type: 'string',
            description: 'The zone to use (e.g., "tk1v", "is1a", "tk1a"). Defaults to "tk1v" if not specified.'
          }
        },
        required: ['appId']
      }
    },
  • Helper function fetchFromAppRunAPI that makes authenticated HTTPS requests to the Sakura Cloud AppRun API. Used by the stop_apprun handler to POST to /applications/{appId}/stop.
    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 for behavioral disclosure. It states the tool stops an application, implying a mutation, but doesn't cover critical aspects like whether this is reversible, requires specific permissions, affects running processes, or has side effects. This is inadequate for a mutation tool with zero 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, direct sentence with no wasted words, making it easy to parse and front-loaded with the core action. It efficiently communicates the essential purpose without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavior, side effects, return values, and usage context, leaving significant gaps for an agent to understand how to invoke it correctly.

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 additional parameter information beyond what's in the schema, resulting in the baseline score of 3 for adequate but no extra value.

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 ('Stop') and target resource ('an AppRun application'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'start_apprun' or 'delete_apprun' beyond the verb, missing explicit comparison that would earn a 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'start_apprun' or 'delete_apprun', nor any prerequisites or context for stopping an application. The description only states what it does, not when or why to use it.

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