ncloud-gov-mcp-server

ncloud_sourcecommit_create_repo

Create a new SourceCommit repository on Naver Cloud Platform. Use dryRun to preview changes before applying.

Instructions

Create a new SourceCommit repository. Use dryRun=true to preview without creating.

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>"
    },
    "name": "ncloud_sourcecommit_create_repo"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Repository name (1-100 chars: English letters, numbers, '-', '_')
`dryRun`	No	If true, returns a preview without actually creating the repository
`fileSafer`	No	Integrate File Safer service (default: false)
`description`	No	Repository description (0-500 bytes)
`objectStorage`	No	Integrate Object Storage service (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only include destructiveHint: false. The description adds valuable context about the dryRun preview behavior, which goes beyond the annotation. It does not contradict the annotation and provides a safety note for a creation operation.

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?

The description is two short sentences with no wasted words. It states the core purpose and the most important usage modifier (dryRun).

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 create tool with fully documented schema parameters, the description is sufficient. It covers the action and a key behavioral option (dryRun). Lack of output schema is not a gap for this simple create operation.

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 provides descriptions for all 5 parameters with 100% coverage. The description does not add parameter-level detail beyond that, so the baseline score of 3 is appropriate.

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 states 'Create a new SourceCommit repository' with a specific verb and resource. This clearly distinguishes it from sibling tools like ncloud_sourcecommit_list_repos, ncloud_sourcecommit_edit_repo, and ncloud_sourcecommit_delete_repo.

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 mentions use of dryRun=true to preview without creating, which is a useful usage hint. However, it does not explicitly compare against alternatives or provide when-not-to-use guidance, though the create operation is self-evident among the sibling tools.

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

Deploy Server