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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_target_groups

DestructiveIdempotent

Remove target groups from your Ncloud account by providing their numbers. Requires explicit confirmation to complete the deletion.

Instructions

⚠️ Destructive: Permanently delete target groups. 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": {
      "targetGroupNoList": "<targetGroupNoList>"
    },
    "name": "ncloud_delete_target_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
targetGroupNoListYesList of target group numbers to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description reinforces this with '⚠️ Destructive' and 'Permanently delete,' adding the irreversibility aspect. It also discloses a critical behavioral requirement: the confirm parameter must be true for the operation to execute. This adds meaningful context beyond the annotation, clarifying both the risk and the safeguard.

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 a clear warning and an explicit conditional for execution. Every word is purposeful, with no filler or repetition. It efficiently conveys the core action, the destructive nature, and the necessary confirmation step.

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?

Given the tool's simplicity (two parameters, no output schema) and the existing annotations, the description is largely complete. It covers the essential context: the action (delete), the target resource (target groups), the permanent impact, and the required confirmation. It could optionally mention that multiple target groups can be deleted at once (implied by the plural schema), but this is not a significant 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 description coverage is 100%, so both parameters are fully documented. The description adds no new semantics beyond the schema: it only restates the confirm requirement. Since the schema already explains each parameter adequately, the description provides marginal additional value, so a 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 clearly states the tool's function: 'Permanently delete target groups.' The verb 'delete' combined with the resource 'target groups' is specific and unambiguous. The name itself also clearly reflects this purpose, and there is no confusion with sibling tools like ncloud_list_target_groups or ncloud_get_target_group_detail.

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 implies usage context by naming the action (delete target groups) and the requirement to set confirm=true for execution. However, it does not explicitly describe when to use this tool versus other related tools, nor does it provide alternative suggestions or exclusions. The guidance is minimal beyond the destructive warning and confirmation prerequisite.

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