ncloud-gov-mcp-server

ncloud_pipeline_list_sourcebuild_projects

Read-only

List available SourceBuild projects to select for pipeline task configuration. Supports pagination and search filtering by project name.

Instructions

List available SourceBuild projects for pipeline task configuration

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_pipeline_list_sourcebuild_projects"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number (1~N)
`pageSize`	No	Items per page (1~N)
`searchWord`	No	Filter by project name (partial match)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, which agrees with 'List'. The description adds the availability scoping ('available') and purpose context, but does not mention pagination behavior, defaults, or return shape. Given annotation coverage, this is acceptable but not rich.

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, front-loaded with verb and resource, contains no filler or redundant information.

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 low-complexity read-only list tool with fully documented schema, the one-line description is sufficient to select and invoke it. However, the absence of any output-schema or return-format guidance is a minor gap.

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 covers all 3 parameters with descriptions (100% coverage), so baseline applies. The description adds no additional parameter-specific semantics beyond the schema.

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?

Description uses specific verb 'List', names resource 'SourceBuild projects', and adds context 'for pipeline task configuration' which distinguishes it from sibling tools like ncloud_sourcebuild_list_projects and ncloud_sourcedeploy_get_sourcebuild_projects.

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 phrase 'for pipeline task configuration' gives a clear context, but there is no explicit guidance on when to use this over alternatives such as ncloud_pipeline_list_sourcedeploy_projects or ncloud_sourcebuild_list_projects, nor any exclusion criteria.

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

Deploy Server