Skip to main content
Glama

ncloud_sourcebuild_create_project

Creates a new SourceBuild project with complete build configuration, including repository, branch, compute, runtime, and optional Docker settings.

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?

Annotations only include destructiveHint=false. The description adds no behavioral context beyond the word 'Create', which is already evident from the tool name. No side effects, resource implications, or required dependencies are disclosed.

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?

A single sentence that is direct and front-loaded. It contains no redundant phrases and earns its place, though it is minimal.

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 tool with 39 parameters, multiple platform-dependent required fields, and no output schema, the one-sentence description is insufficient. It does not orient the agent to different build platform modes (SourceBuild vs ContainerRegistry vs PublicRegistry) or the need for prerequisite lookup tools, leaving the agent to rely entirely on the extensive schema.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description's 'full configuration' adds no parameter-specific meaning beyond what the schema already provides.

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 uses a specific verb 'Create' with a specific resource 'SourceBuild project', clearly distinguishing it from sibling tools like ncloud_sourcecommit_create_repo and ncloud_sourcedeploy_create_project. The phrase 'new' reinforces the creation scope.

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 a new project but provides no explicit guidance on when to use it vs. alternatives. It does not mention prerequisites (e.g., listing OS, compute, or runtime IDs first) or any exclusion conditions, leaving the agent to infer context from the name and schema.

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-gov-mcp-server'

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