Skip to main content
Glama
tao12345666333

Civo MCP Server

list_instances

Retrieve a paginated list of Civo cloud instances, optionally filtered by region.

Instructions

List all instances on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoFilter by region
pageNoPagination page
per_pageNoResults per page

Implementation Reference

  • The tool handler for 'list_instances' - calls listInstances API, formats the output with hostname, ID, status, and public IP.
    case 'list_instances': {
      const instances = await listInstances(args);
      const instanceList = instances.items
        .map(
          i =>
            `${i.hostname} (${i.id}) - ${i.status} - Public IP: ${i.public_ip || 'None'}`
        )
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Instances:\n${instanceList}`,
          },
        ],
        isError: false,
      };
    }
  • The tool schema definition for 'list_instances' - includes name, description, and inputSchema with optional region, page, and per_page parameters.
    export const LIST_INSTANCES_TOOL: Tool = {
      name: 'list_instances',
      description: 'List all instances on Civo',
      inputSchema: {
        type: 'object',
        properties: {
          region: {
            type: 'string',
            description: 'Filter by region',
          },
          page: {
            type: 'number',
            description: 'Pagination page',
            default: 1,
          },
          per_page: {
            type: 'number',
            description: 'Results per page',
            default: 20,
          },
        },
      },
    };
  • src/index.ts:72-72 (registration)
    Registration of LIST_INSTANCES_TOOL in the server's capabilities.
    [LIST_INSTANCES_TOOL.name]: LIST_INSTANCES_TOOL,
  • The API helper function that makes the actual HTTP GET request to Civo's /v2/instances endpoint with optional query parameters (region, page, per_page).
    export async function listInstances(params: {
      region?: string;
      page?: number;
      per_page?: number;
    }): Promise<CivoInstanceList> {
      checkRateLimit();
    
      const url = new URL(`${CIVO_API_URL}/instances`);
      if (params.region) url.searchParams.set('region', params.region);
      if (params.page) url.searchParams.set('page', params.page.toString());
      if (params.per_page)
        url.searchParams.set('per_page', params.per_page.toString());
    
      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();
    }
  • The CivoInstanceList interface defining the response shape (items array, page, per_page, pages) returned by listInstances.
    export interface CivoInstanceList {
      items: CivoInstance[];
      page: number;
      per_page: number;
      pages: number;
    }
Behavior2/5

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

With no annotations, the description should convey behavioral traits. It only states 'list all instances' without disclosing whether it is read-only, resource-intensive, or requires specific permissions. The agent lacks essential behavioral cues.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (four words) but underspecified. It fits the minimalism but sacrifices necessary detail, making it borderline adequate.

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?

Without an output schema, the description should explain what is returned. It does not mention response format, pagination behavior, or the effect of filtering. The presence of optional pagination parameters is not explained, leaving gaps.

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?

All three parameters have descriptions in the input schema (100% coverage), so the schema already documents their meaning. The description adds no additional context beyond what the schema provides, meeting the baseline of 3.

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 'List all instances on Civo' clearly states the verb 'List', the resource 'instances', and the platform. It effectively distinguishes this tool from sibling tools like create_instance, delete_instance, etc., which have different actions.

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 list_disk_images or list_kubernetes_clusters. The description does not mention filtering, pagination, or context for choosing this tool.

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