Skip to main content
Glama
tao12345666333

Civo MCP Server

reboot_instance

Restart a Civo cloud instance by providing its ID and region to resolve issues or apply updates.

Instructions

Reboot a cloud instance on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInstance ID
regionYesRegion identifier

Implementation Reference

  • The actual API handler function that sends a POST request to the Civo API to reboot an instance. It accepts { id, region } parameters, calls the Civo API endpoint /v2/instances/{id}/reboots, and returns the JSON response.
    export async function rebootInstance(params: {
      id: string;
      region: string;
    }): Promise<any> {
      checkRateLimit();
    
      const url = `${CIVO_API_URL}/instances/${params.id}/reboots`;
      const response = await fetch(url, {
        method: 'POST',
        headers: {
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
        body: new URLSearchParams({
          region: params.region,
        }),
      });
    
      if (!response.ok) {
        throw new Error(
          `Civo API error: ${response.status} ${response.statusText}`
        );
      }
    
      return response.json();
    }
  • The tool schema definition for 'reboot_instance'. Defines inputSchema with required 'id' (string) and 'region' (string) properties, and a description explaining it reboots a cloud instance on Civo.
    export const REBOOT_INSTANCE_TOOL: Tool = {
      name: 'reboot_instance',
      description: 'Reboot a cloud instance on Civo',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Instance ID',
          },
          region: {
            type: 'string',
            description: 'Region identifier',
          },
        },
        required: ['id', 'region'],
      },
    };
  • src/index.ts:63-93 (registration)
    Server registration: REBOOT_INSTANCE_TOOL is registered in the server's tool capabilities, making it available for listing and calling via MCP.
    const server = new Server(
      {
        name: 'example-servers/civo',
        version: '0.1.0',
      },
      {
        capabilities: {
          tools: {
            [CREATE_INSTANCE_TOOL.name]: CREATE_INSTANCE_TOOL,
            [LIST_INSTANCES_TOOL.name]: LIST_INSTANCES_TOOL,
            [REBOOT_INSTANCE_TOOL.name]: REBOOT_INSTANCE_TOOL,
            [SHUTDOWN_INSTANCE_TOOL.name]: SHUTDOWN_INSTANCE_TOOL,
            [START_INSTANCE_TOOL.name]: START_INSTANCE_TOOL,
            [RESIZE_INSTANCE_TOOL.name]: RESIZE_INSTANCE_TOOL,
            [DELETE_INSTANCE_TOOL.name]: DELETE_INSTANCE_TOOL,
            [LIST_DISK_IMAGES_TOOL.name]: LIST_DISK_IMAGES_TOOL,
            [GET_DISK_IMAGE_TOOL.name]: GET_DISK_IMAGE_TOOL,
            [LIST_SIZES_TOOL.name]: LIST_SIZES_TOOL,
            [LIST_REGIONS_TOOL.name]: LIST_REGIONS_TOOL,
            [LIST_NETWORKS_TOOL.name]: LIST_NETWORKS_TOOL,
            [CREATE_NETWORK_TOOL.name]: CREATE_NETWORK_TOOL,
            [RENAME_NETWORK_TOOL.name]: RENAME_NETWORK_TOOL,
            [DELETE_NETWORK_TOOL.name]: DELETE_NETWORK_TOOL,
            [LIST_KUBERNETES_CLUSTERS_TOOL.name]: LIST_KUBERNETES_CLUSTERS_TOOL,
            [CREATE_KUBERNETES_CLUSTER_TOOL.name]: CREATE_KUBERNETES_CLUSTER_TOOL,
            [DELETE_KUBERNETES_CLUSTER_TOOL.name]: DELETE_KUBERNETES_CLUSTER_TOOL,
            [LIST_KUBERNETES_VERSIONS_TOOL.name]: LIST_KUBERNETES_VERSIONS_TOOL,
          },
        },
      }
    );
  • src/index.ts:96-118 (registration)
    ListTools handler: REBOOT_INSTANCE_TOOL is included in the array of tools returned when clients list available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        CREATE_INSTANCE_TOOL,
        LIST_INSTANCES_TOOL,
        REBOOT_INSTANCE_TOOL,
        SHUTDOWN_INSTANCE_TOOL,
        START_INSTANCE_TOOL,
        RESIZE_INSTANCE_TOOL,
        DELETE_INSTANCE_TOOL,
        LIST_DISK_IMAGES_TOOL,
        GET_DISK_IMAGE_TOOL,
        LIST_SIZES_TOOL,
        LIST_REGIONS_TOOL,
        LIST_NETWORKS_TOOL,
        CREATE_NETWORK_TOOL,
        RENAME_NETWORK_TOOL,
        DELETE_NETWORK_TOOL,
        LIST_KUBERNETES_CLUSTERS_TOOL,
        CREATE_KUBERNETES_CLUSTER_TOOL,
        DELETE_KUBERNETES_CLUSTER_TOOL,
        LIST_KUBERNETES_VERSIONS_TOOL,
      ],
    }));
  • CallToolRequestHandler case 'reboot_instance': validates that args has id (string) and region (string), calls the rebootInstance API function, and returns a success message with the result.
    case 'reboot_instance': {
      if (
        typeof args !== 'object' ||
        args === null ||
        typeof args.id !== 'string' ||
        typeof args.region !== 'string'
      ) {
        throw new Error('Invalid arguments for reboot_instance');
      }
    
      const result = await rebootInstance(
        args as { id: string; region: string }
      );
      return {
        content: [
          {
            type: 'text',
            text: `Instance ${args.id} rebooted: ${result.result}`,
          },
        ],
        isError: false,
      };
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description does not disclose side effects, permissions, or behavioral nuances beyond the basic reboot action.

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?

Single sentence, no wasted words, appropriately concise.

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?

Minimal but sufficient for a simple reboot tool, though lacks usage guidance and behavioral details.

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 covers 100% of parameters with descriptions, so baseline is 3; description adds no extra semantic meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (reboot) and resource (cloud instance on Civo), distinguishing it from sibling tools like shutdown_instance or start_instance.

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 on when to use this tool over alternatives (e.g., shutdown + start) or prerequisites.

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/tao12345666333/civo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server