Skip to main content
Glama
tao12345666333

Civo MCP Server

list_sizes

List available instance sizes on Civo for selecting compute resources when provisioning instances.

Instructions

List available instance sizes on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'list_sizes': calls listSizes() API function and formats the output with size name and description.
    case 'list_sizes': {
      const sizes = await listSizes();
      const sizeList = sizes
        .map((s: any) => `${s.name} - ${s.description}`)
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Available Sizes:\n${sizeList}`,
          },
        ],
        isError: false,
      };
    }
  • The API function listSizes() that fetches sizes from the Civo API endpoint /sizes.
    export async function listSizes(): Promise<Size[]> {
      const url = `${CIVO_API_URL}/sizes`;
      const response = await fetch(url, {
        headers: {
          'Content-Type': 'application/json',
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
      });
    
      if (!response.ok) {
        throw new Error(`Failed to list sizes: ${response.statusText}`);
      }
    
      return await response.json();
    }
  • Tool definition/schema for 'list_sizes' with name, description, and empty inputSchema.
    export const LIST_SIZES_TOOL: Tool = {
      name: 'list_sizes',
      description: 'List available instance sizes on Civo',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    };
  • src/index.ts:80-80 (registration)
    Registration of LIST_SIZES_TOOL in the server's tools capabilities.
    [LIST_SIZES_TOOL.name]: LIST_SIZES_TOOL,
  • src/index.ts:107-107 (registration)
    Registration of LIST_SIZES_TOOL in the ListTools response.
    LIST_SIZES_TOOL,
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does not mention any behavioral traits like pagination, auth requirements, or sorting. For a simple list with no parameters, this is acceptable but could be improved.

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?

A single, concise sentence with no wasted words. It is 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?

Given no output schema and no parameters, the description is adequate but could be more informative by detailing the return value (e.g., size names or specs).

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?

There are no parameters (schema coverage 100%), so the baseline is 4. The description adds no parameter-specific meaning, but none is needed.

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 tool lists available instance sizes on Civo, with a specific verb and resource. It distinguishes from sibling tools like 'list_instances' and 'create_instance'.

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?

No explicit guidance on when to use or when not to use. However, the tool's simplicity and lack of alternatives for listing sizes make it self-explanatory, so a middle score is appropriate.

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