Skip to main content
Glama
tao12345666333

Civo MCP Server

list_regions

Retrieve a list of available regions on Civo for deploying cloud resources.

Instructions

List available regions on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handles the 'list_regions' tool call by invoking listRegions() API function and formatting region names/codes into a text response.
    case 'list_regions': {
      const regions = await listRegions();
      const regionList = regions
        .map((r: any) => `${r.name} (${r.code})`)
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Available Regions:\n${regionList}`,
          },
        ],
        isError: false,
      };
    }
  • Defines the tool schema for 'list_regions' with no required input parameters.
    export const LIST_REGIONS_TOOL: Tool = {
      name: 'list_regions',
      description: 'List available regions on Civo',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    };
  • API helper that fetches regions from the Civo API endpoint (https://api.civo.com/v2/regions) with Bearer token auth.
    export async function listRegions(): Promise<Region[]> {
      const url = `${CIVO_API_URL}/regions`;
      const response = await fetch(url, {
        headers: {
          'Content-Type': 'application/json',
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
      });
    
      if (!response.ok) {
        throw new Error(`Failed to list regions: ${response.statusText}`);
      }
    
      return await response.json();
    }
  • src/index.ts:108-108 (registration)
    Registers the tool in the ListToolsRequestHandler, making it available in the tools list.
    LIST_REGIONS_TOOL,
  • src/index.ts:81-81 (registration)
    Registers the tool in the server capabilities on construction.
    [LIST_REGIONS_TOOL.name]: LIST_REGIONS_TOOL,
Behavior2/5

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

No annotations provided, and description only states 'List available regions' without disclosing read-only nature, potential limitations, or return format.

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 with no wasted words. Front-loaded and efficient.

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 adequate for a parameterless list tool. Lacks details about output or behavior, but no output schema exists to supplement.

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?

No parameters exist, so schema coverage is 100%. Description doesn't need to add param info; baseline of 4 applies.

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

Purpose4/5

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

Describes verb 'List' and resource 'available regions on Civo'. Clearly distinguishes from sibling list tools that target different resources like instances or disk images.

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. Lacks context or exclusions.

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