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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_sourcedeploy_delete_scenario

DestructiveIdempotent

Delete a deployment scenario by specifying project, stage, and scenario IDs. Set confirm=true to execute this destructive action and avoid accidental removals.

Instructions

⚠️ Destructive: Delete a deployment scenario. 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>",
      "stageId": "<stageId>",
      "scenarioId": "<scenarioId>"
    },
    "name": "ncloud_sourcedeploy_delete_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
stageIdYesID of the deployment stage
projectIdYesID of the deployment project
scenarioIdYesID of the deployment scenario to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description reinforces this with '⚠️ Destructive'. It adds the critical behavioral detail that confirm=true is required for the operation to actually execute, which goes beyond the annotation and provides important safety context.

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, compact sentence, front-loaded with a warning icon and the destructive nature. Every word earns its place, with no redundancy or fluff.

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 tool with a simple parameter set and fully documented schema, the description covers the essential information: the destructive action, the confirmation requirement, and the resource type. It does not explain broader implications, but those are not necessary for correct invocation given the annotations and 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?

All four parameters have schema descriptions, giving 100% coverage. The description adds meaningful context for the confirm parameter, explaining it must be true to execute, which complements the schema's default value. Other parameters are already well-documented in the schema, so no additional description is needed.

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 verb 'Delete' and the resource 'deployment scenario', making the purpose explicit. It distinguishes itself from sibling delete tools (e.g., delete_stage, delete_project) by specifying the scenario resource.

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

Usage Guidelines2/5

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

The description provides the prerequisite that confirm=true must be set to execute, but gives no guidance on when to use this tool versus alternatives or when not to use it. It lacks contextual direction beyond the safety condition.

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