OCI MCP Server

create_cluster

Create an OKE cluster by providing compartment, name, VCN, and Kubernetes version. Node pools are added separately.

Instructions

Create an OKE cluster (basic; node pool added separately).

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>",
      "name": "<name>",
      "vcn_id": "<vcn_id>",
      "kubernetes_version": "<kubernetes_version>"
    },
    "name": "create_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`compartment_id`	Yes
`name`	Yes
`vcn_id`	Yes
`kubernetes_version`	Yes
`service_subnet_id`	No
`pod_subnet_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must disclose behaviors. It only states 'basic' but lacks details on idempotency, destruction, authentication, rate limits, or side effects.

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, concise, and front-loaded with action. No unnecessary words; clearly communicates the purpose.

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?

With 6 parameters, 4 required, no output schema, and no annotations, the description is too minimal. It does not explain prerequisites, return values, or what 'basic' entails.

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?

Schema description coverage is 0%, and description does not explain any parameters. It adds no meaning beyond the schema fields themselves.

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?

Description clearly states it creates an OKE cluster, specifying 'basic' and that node pool is added separately. This is specific and distinguishes from other creation tools like create_bucket or create_vcn.

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?

Implies that this tool is for the initial cluster creation, with node pool added separately, but does not explicitly mention when to use or not use it compared to alternatives. No direct reference to siblings.

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

Deploy Server