Skip to main content
Glama
tao12345666333

Civo MCP Server

list_kubernetes_versions

Retrieve available Kubernetes versions from Civo for cluster provisioning and upgrades.

Instructions

List available Kubernetes versions on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the tool schema/name for list_kubernetes_versions with no required input params
    export const LIST_KUBERNETES_VERSIONS_TOOL: Tool = {
      name: 'list_kubernetes_versions',
      description: 'List available Kubernetes versions on Civo',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    };
  • Handler case that calls listAvailableVersions API helper and formats the response
    case 'list_kubernetes_versions': {
      const versions = await listAvailableVersions();
      const versionList = versions
        .map((v: any) => `${v.Version} - ${v.Label} (${v.Type}) [${v.ClusterType}]${v.Default ? ' *DEFAULT*' : ''}`)
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Available Kubernetes Versions:\n${versionList}`,
          },
        ],
        isError: false,
      };
    }
  • Makes the actual API call to Civo's /kubernetes/versions endpoint and returns the version data
    export async function listAvailableVersions(): Promise<
      CivoKubernetesVersion[]
    > {
      checkRateLimit();
    
      const url = `${CIVO_API_URL}/kubernetes/versions`;
      const response = await fetch(url, {
        headers: {
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
      });
    
      if (!response.ok) {
        throw new Error(
          `Civo API error: ${response.status} ${response.statusText}`
        );
      }
    
      return response.json();
    }
  • Type definition for the Kubernetes version objects returned by the API
    export interface CivoKubernetesVersion {
      Version: string;
      Label: string;
      Type: string;
      Release: string;
      Default: boolean;
      ClusterType: string;
    }
  • src/index.ts:89-89 (registration)
    Registration of the tool in the server's tool list
    [LIST_KUBERNETES_VERSIONS_TOOL.name]: LIST_KUBERNETES_VERSIONS_TOOL,
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the operation is to list versions, which implies a read-only action, but it does not explicitly confirm non-destructiveness, rate limits, or behavior under error conditions. Minimal but adequate.

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 wasted words. It is front-loaded with the key action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is complete enough. It clearly states what the tool does, which is sufficient for an agent to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so the description does not need to add parameter information. Baseline of 4 is appropriate as no param info is required.

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 verb 'List', the resource 'available Kubernetes versions', and the platform 'on Civo'. It unambiguously distinguishes from sibling tools like 'list_kubernetes_clusters'.

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 provides no explicit guidance on when to use this tool versus alternatives. It is implied that it should be used before creating a cluster, but no when-not or alternative tools are mentioned.

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