Skip to main content
Glama
Sign In
OCI MCP Server

OCI MCP Server

by sarthak-pansare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_vcn

Create a Virtual Cloud Network in Oracle Cloud Infrastructure, specifying the compartment and display name, with optional CIDR block and DNS label.

Instructions

Create a VCN.

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": {
      "compartment_id": "<compartment_id>",
      "display_name": "<display_name>"
    },
    "name": "create_vcn"
  }
}

Input Schema

NameRequiredDescriptionDefault
compartment_idYes
display_nameYes
cidr_blockNo10.0.0.0/16
dns_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as mutability, authorization needs, or side effects. The agent receives zero transparency.

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

Conciseness2/5

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

Extremely concise at 4 words, but this under-specification is not beneficial. The description omits crucial details and does not earn its place as it fails to inform.

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

Completeness1/5

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

Given the complexity of the tool (4 parameters, no output schema, no annotations), the description is completely inadequate. It does not cover return values, parameter dependencies, or any contextual nuance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter schema coverage is 0%, and the description provides no additional meaning for parameters like compartment_id, display_name, cidr_block, or dns_label.

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

Purpose3/5

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

The description 'Create a VCN' clearly states the verb and resource, but lacks specificity about what a VCN is or how it differs from sibling tools like create_subnet. It is adequate but minimal.

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 such as add_default_route or create_internet_gateway. No prerequisites or exclusions are mentioned.

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

Deploy Server

Other Tools