Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_sourcebuild_delete_project

DestructiveIdempotent

Permanently delete a SourceBuild project and its build history. Set confirm=true to execute.

Instructions

⚠️ Destructive: Permanently delete a SourceBuild project and all its build history. Set confirm=true to execute.

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": {
      "projectId": "<projectId>"
    },
    "name": "ncloud_sourcebuild_delete_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute the destructive operation
projectIdYesProject ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses that deletion is permanent and includes all build history, going beyond the destructiveHint annotation. It also reveals the requirement to 'Set confirm=true to execute,' which is essential behavioral information not present in the annotations.

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 with no wasted words. It includes a warning emoji, the action, the affected resource, and the critical confirm requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with two parameters and no output schema, the description fully covers the essential context: what is deleted, permanence, and the safety gate. It does not need to explain return values or alternative tools.

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 value by explaining the confirm parameter's role, but it largely echoes the schema's own description ('Must be true to execute the destructive operation'), providing no new semantic detail.

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 the tool's action: 'Permanently delete a SourceBuild project and all its build history.' It uses a specific verb and resource, distinguishing it from sibling tools like ncloud_sourcebuild_list_projects and ncloud_sourcebuild_get_project.

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 makes the usage context clear—delete a project when you no longer need it—and emphasizes the destructive, permanent nature. It does not explicitly name alternatives or exclusions, but the context is unambiguous for a delete operation.

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

Deploy Server

Other Tools