Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_sourcebuild_create_project

Create a new SourceBuild project with custom build commands, environment variables, and artifact storage. Configure platform type, runtime, and Docker engine as needed.

Instructions

Create a new SourceBuild project with full configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoImage tag (required if platformType=ContainerRegistry|PublicRegistry)
nameYesProject name (alphanumeric, '_', '-', 1-80 chars)
osIdNoOS ID (required if platformType=SourceBuild, from list_os)
imageNoImage name (required if platformType=ContainerRegistry|PublicRegistry)
branchYesBranch to build from
envVarsNoBuild environment variables
timeoutNoBuild timeout in minutes (5-540, default: 5)
cacheTagNoCache image tag
cacheUseNoSave build image after completion
dockerIdNoDocker engine version ID (required if dockerUse=true, from list_docker_engines)
computeIdYesCompute type ID (from list_compute)
dockerUseNoInclude Docker engine for build
runtimeIdNoRuntime type ID (required if platformType=SourceBuild, from list_runtimes)
cacheImageNoCache image name
repositoryYesSource repository name
sourceTypeNoSource repository type (SourceCommit)SourceCommit
artifactUseNoSave build artifacts
cacheLatestNoSet latest tag for cache
descriptionNoProject description
artifactPathNoBuild artifact paths
platformTypeNoPlatform type: SourceBuild | ContainerRegistry | PublicRegistrySourceBuild
registryNameNoContainer Registry name (required if platformType=ContainerRegistry)
buildCommandsNoBuild commands
cacheRegistryNoContainer Registry for cache
artifactBackupNoBackup artifacts
artifactBucketNoObject Storage bucket for artifacts
dockerbuildTagNoDocker build image tag
dockerbuildUseNoEnable Docker image build
linkedFileSaferNoEnable File Safer integration
artifactFilenameNoArtifact filename
dockerbuildImageNoDocker build image name
preBuildCommandsNoPre-build commands
runtimeVersionIdNoRuntime version ID (required if platformType=SourceBuild, from list_runtime_versions)
dockerbuildLatestNoSet latest tag for Docker build
postBuildCommandsNoPost-build commands
artifactStoragePathNoPath within bucket
dockerbuildRegistryNoDocker build target Container Registry name
dockerbuildDockerfileNoDockerfile path
linkedCloudLogAnalyticsNoEnable Cloud Log Analytics integration
Behavior2/5

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

The description does not disclose any behavioral traits beyond what annotations provide (destructiveHint: false). It lacks details on side effects, authentication requirements, rate limits, or consequences of creation (e.g., name uniqueness). With minimal annotation coverage, the description fails to inform the agent adequately.

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

Conciseness4/5

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

The description is very concise at one sentence. It is front-loaded with the key action and resource. However, for a tool with 39 parameters, it could benefit from a brief structured overview of key aspects.

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?

Given the tool's complexity (39 parameters, no output schema, minimal annotations), the description is severely lacking. It does not explain return values, success behavior, error conditions, or important constraints. A more complete description is necessary for effective agent use.

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 the baseline is 3. The description adds no additional meaning beyond 'with full configuration', which is already implied by the many parameters. It does not compensate for any gaps or provide context for parameter usage.

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 'Create a new SourceBuild project with full configuration', specifying the action (create) and resource (SourceBuild project). It effectively distinguishes this tool from siblings like ncloud_sourcebuild_update_project and ncloud_sourcebuild_delete_project.

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?

The description implies usage for creating new projects but offers no explicit guidelines on when to use this tool versus alternatives, nor does it mention prerequisites or scenarios where it should not be used. For a tool with many sibling creation tools, this is adequate but not helpful.

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/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server