Skip to main content
Glama
tao12345666333

Civo MCP Server

delete_network

Delete a network on Civo cloud by specifying its ID and region.

Instructions

Delete a network on Civo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNetwork ID
regionNoRegion identifier

Implementation Reference

  • The actual API handler that performs the DELETE request to the Civo API to delete a network by ID and region.
    export async function deleteNetwork(params: {
      id: string;
      region: string;
    }): Promise<any> {
      const url = new URL(`${CIVO_API_URL}/networks/${params.id}`);
      url.searchParams.set('region', params.region);
    
      const response = await fetch(url.toString(), {
        method: 'DELETE',
        headers: {
          Authorization: `Bearer ${CIVO_API_KEY}`,
        },
      });
    
      if (!response.ok) {
        throw new Error(`Failed to delete network: ${response.statusText}`);
      }
    
      return await response.json();
    }
  • The Tool definition with inputSchema for the delete_network tool, specifying required field 'id' and optional 'region'.
    export const DELETE_NETWORK_TOOL: Tool = {
      name: 'delete_network',
      description: 'Delete a network on Civo',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Network ID',
          },
          region: {
            type: 'string',
            description: 'Region identifier',
          },
        },
        required: ['id'],
      },
    };
  • src/index.ts:85-85 (registration)
    Registration of DELETE_NETWORK_TOOL in the server's tool capabilities map.
    [DELETE_NETWORK_TOOL.name]: DELETE_NETWORK_TOOL,
  • src/index.ts:112-112 (registration)
    Inclusion of DELETE_NETWORK_TOOL in the list of tools returned by ListToolsRequestSchema handler.
    DELETE_NETWORK_TOOL,
  • The call tool request handler that validates arguments for 'delete_network' and invokes the deleteNetwork API function.
    case 'delete_network': {
      if (
        typeof args !== 'object' ||
        args === null ||
        typeof args.id !== 'string'
      ) {
        throw new Error('Invalid arguments for delete_network');
      }
    
      const result = await deleteNetwork(
        args as { id: string; region: string }
      );
      return {
        content: [
          {
            type: 'text',
            text: `Deleted network ${args.id}: ${result.result}`,
          },
        ],
        isError: false,
      };
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action is deletion, but does not mention consequences (e.g., whether the network must be empty, if deletion is irreversible, or required permissions).

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 very short (one phrase), but it barely adds value beyond the tool name. It is not structured or front-loaded with key details; the single sentence could be considered under-specified.

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?

For a simple deletion tool, the description lacks essential context such as whether deletion can be undone, effects on associated resources, or error conditions. No output schema, so return value details are missing.

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?

Schema coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what the schema already provides for id and region.

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 'Delete' and the resource 'network on Civo', distinguishing it from sibling delete tools (delete_instance, delete_kubernetes_cluster) which operate on different resources.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., rename_network) or under what conditions deletion is appropriate. No prerequisites or cautionary notes.

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