Skip to main content
Glama

Create a private network

create_vpc

Creates an isolated private network; ready when the call returns. The first usable address (.1) is reserved for the gateway. Scope: network.write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "cidr": "<cidr>",
      "region": "<region>"
    },
    "name": "create_vpc"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidrYesPrivate IPv4 range from /16 to /29 in 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16, e.g. 10.0.0.0/24.
nameYesDisplay name of the network, 1 to 64 characters.
regionYesRegion slug from list_regions, e.g. montreal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Display name of the network, 1 to 64 characters."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, open-world operation with no destructive hint, so the safety profile is covered. The description genuinely adds beyond that: the operation is synchronous ("ready when the call returns"), the gateway occupies .1, and network.write authorization is required. Missing only failure/idempotency behavior, e.g. what happens on a name collision.

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?

Three tight clauses with zero filler, and the core action plus its synchronous completion are front-loaded. The scope note is short and useful rather than padding.

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

Completeness4/5

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

For a small three-parameter creation tool with no output schema, the description covers timing, addressing layout and required authorization, which is most of what an agent needs. It still never states what the call returns (e.g. a network identifier to use with connect_vpc), which matters precisely because no output schema exists.

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?

Schema coverage is 100%, so cidr, name and region are already documented, and that sets a baseline of 3. The description earns an extra point by noting that the first usable address (.1) is reserved for the gateway, which constrains how an agent should pick a CIDR and avoids an off-by-one addressing mistake.

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?

The description opens with a specific verb and resource ("Creates an isolated private network"), which cleanly separates it from connect_vpc, get_vpc, move_vpc and delete_vpc. It does not explicitly name a sibling or contrast with one, which keeps it short of a 5.

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?

There is no when-to-use or when-not-to-use guidance: nothing says when to provision a new network versus connecting an existing one, or what the prerequisites are beyond a bare scope string. The agent must infer the usage context from the verb alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.