Skip to main content
Glama
tao12345666333

Civo MCP Server

list_disk_images

Retrieve available disk images for a specified region to select an operating system for Civo cloud instances.

Instructions

List available disk images on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoRegion identifier

Implementation Reference

  • Main handler that calls the Civo API to list disk images, with optional region filtering.
    export async function listDiskImages(params: {
      region?: string;
    }): Promise<CivoDiskImageList> {
      checkRateLimit();
    
      const url = new URL(`${CIVO_API_URL}/disk_images`);
      if (params.region) url.searchParams.set('region', params.region);
    
      const response = await fetch(url.toString(), {
        headers: {
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
      });
    
      if (!response.ok) {
        throw new Error(
          `Civo API error: ${response.status} ${response.statusText}`
        );
      }
    
      return { items: await response.json() };
    }
  • Server-side handler in the CallToolRequestSchema that dispatches to the API function and formats the response.
    case 'list_disk_images': {
      const images = await listDiskImages(args);
      const imageList = images.items
        .map(
          i =>
            `${i.name} (${i.id}) - ${i.distribution} ${i.version} - ${i.state}`
        )
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Disk Images:\n${imageList}`,
          },
        ],
        isError: false,
      };
    }
  • Tool schema definition with name, description, and input schema (accepts optional region string).
    export const LIST_DISK_IMAGES_TOOL: Tool = {
      name: 'list_disk_images',
      description: 'List available disk images on Civo',
      inputSchema: {
        type: 'object',
        properties: {
          region: {
            type: 'string',
            description: 'Region identifier',
          },
        },
      },
    };
  • Type definitions for the disk image list response.
    export interface CivoDiskImageList {
      items: CivoDiskImage[];
    }
  • src/index.ts:78-90 (registration)
    Tool registration in the server capabilities object.
      [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,
    },
Behavior3/5

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

The description implies a read-only operation but lacks details on authentication requirements, pagination, or ordering. With no annotations, it provides minimal behavioral context beyond listing.

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, front-loaded sentence with no extraneous information. Every word serves a purpose.

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?

For a simple list tool with one optional parameter, the description is adequate but lacks information on return format, default region behavior, or typical usage scenarios.

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 coverage is 100% for the single parameter 'region', but its description only repeats 'Region identifier'. The tool description adds no extra semantics; baseline score of 3 applies.

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 (list) and resource (disk images) with scope (on Civo). It effectively distinguishes from 'get_disk_image' and other list tools.

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 versus alternatives. No mention of prerequisites, filtering, or context such as listing images for a specific purpose.

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