ncloud-gov-mcp-server

ncloud_sourcedeploy_list_projects

Read-only

List SourceDeploy deployment projects with optional name filtering to track and manage your deployment history.

Instructions

List all SourceDeploy deployment projects with optional name filter

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_sourcedeploy_list_projects"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number (default: 1)
`pageSize`	No	Number of items per page (default: 100, max: 100)
`projectName`	No	Filter by project name (partial match)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares the safe, non-mutating nature. The description adds the 'all' scope and optional name filter, which is useful, but it does not mention pagination behavior, response format, or any other behavioral details. Since the annotation covers the main safety aspect, a 3 is appropriate.

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 a single, front-loaded sentence: verb first, then resource, then optional filter. No redundant words or filler. It is optimally concise.

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 simple list tool with all-optional parameters and a readOnlyHint annotation, the description adequately covers the purpose and the main filter. There is no output schema, but 'List all ... projects' implies a collection response. It is sufficiently complete for the agent to select and invoke the tool correctly.

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% — each parameter (pageNo, pageSize, projectName) has a clear description in the schema. The tool description only restates 'name filter' for projectName and does not add additional meaning. Baseline 3 applies because the schema does the heavy lifting.

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 'List' and identifies the resource as 'SourceDeploy deployment projects', clearly distinguishing it from sibling tools like ncloud_sourcedeploy_list_stages or ncloud_sourcebuild_list_projects. It also mentions the optional name filter, which adds precision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for read-only listing of SourceDeploy projects and indicates the optional filter. It does not explicitly state when not to use it or name alternatives, but the purpose is clear enough for a simple list operation. No exclusions are present.

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

Deploy Server