Skip to main content
Glama
tao12345666333

Civo MCP Server

get_disk_image

Retrieve details of a specific disk image by providing its ID and optionally a region identifier.

Instructions

Get details of a specific disk image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDisk image ID
regionNoRegion identifier

Implementation Reference

  • Tool schema registration for 'get_disk_image' - defines name, description, and input schema (id required, region optional).
    export const GET_DISK_IMAGE_TOOL: Tool = {
      name: 'get_disk_image',
      description: 'Get details of a specific disk image',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Disk image ID',
          },
          region: {
            type: 'string',
            description: 'Region identifier',
          },
        },
        required: ['id'],
      },
    };
  • src/index.ts:79-93 (registration)
    Tool registration - maps GET_DISK_IMAGE_TOOL.name to the tool definition in the server's capabilities.
            [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:106-118 (registration)
    Lists GET_DISK_IMAGE_TOOL in the ListToolsRequestSchema handler so it's exposed to clients.
        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,
      ],
    }));
  • Call handler for 'get_disk_image' - validates args (id must be string), calls getDiskImage API function, formats response with image details.
    case 'get_disk_image': {
      if (
        typeof args !== 'object' ||
        args === null ||
        typeof args.id !== 'string'
      ) {
        throw new Error('Invalid arguments for get_disk_image');
      }
    
      const image = await getDiskImage({
        id: args.id as string,
        region: args.region as string,
      });
    
      return {
        content: [
          {
            type: 'text',
            text:
              'Disk Image Details:\n' +
              `ID: ${image.id}\n` +
              `Name: ${image.name}\n` +
              `Version: ${image.version}\n` +
              `State: ${image.state}\n` +
              `Distribution: ${image.distribution}\n` +
              `Description: ${image.description || 'None'}\n` +
              `Label: ${image.label || 'None'}`,
          },
        ],
        isError: false,
      };
    }
  • API helper function getDiskImage - makes HTTP GET request to Civo API /v2/disk_images/{id} with region parameter, returns parsed JSON as CivoDiskImage.
    export async function getDiskImage(params: {
      id: string;
      region: string;
    }): Promise<CivoDiskImage> {
      checkRateLimit();
    
      const url = new URL(`${CIVO_API_URL}/disk_images/${params.id}`);
      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 response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only states 'Get details' without indicating that the operation is read-only, whether authorization is needed, or any side effects. This leaves significant gaps 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 concise sentence with no superfluous words. It is front-loaded and efficiently communicates the tool's 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?

Given the absence of an output schema, the description should hint at return values, but it only says 'details'. The tool has a sibling list_disk_images, but no guidance is provided on how parameters affect results. This completeness gap keeps it at an adequate but not exceptional level.

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 covers both parameters with descriptions (100% coverage), so the baseline is 3. The description does not add additional semantics or constraints beyond the schema, thus meeting but not exceeding expectations.

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 'Get details of a specific disk image' clearly states the action (Get) and target (specific disk image), distinguishing it from sibling tools like list_disk_images which retrieves all disk images. This meets the criteria for specific verb+resource and differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a specific disk image ID, but it lacks explicit guidance on when to use this versus alternatives like list_disk_images. No context or exclusions are provided, relying on the agent to infer usage.

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