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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_detach_policy_from_group

DestructiveIdempotent

Remove one or more IAM policies from a group to revoke attached permissions. Set confirm=true to apply the change.

Instructions

⚠️ Destructive: Remove one or more IAM policies from a group. Policy IDs are sent in the request body as policyIdList (the API takes no policy ID in the path). 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": {
      "groupId": "<groupId>"
    },
    "name": "ncloud_detach_policy_from_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute
groupIdYesGroup ID
policyIdNoSingle policy ID to detach. Merged into policyIdList when sent; kept for backward compatibility
policyIdListNoList of policy IDs to detach. Provide this or policyId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.12.0
    • changedInput schema / properties / policyId / description
      Previous value: -"Policy ID to detach"New value: +"Single policy ID to detach. Merged into policyIdList when sent; kept for backward compatibility"
    • addedInput schema / properties / policyIdList
      Added value: +{
+  "description": "List of policy IDs to detach. Provide this or policyId",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "groupId",
-  "policyId"
-]New value: +[
+  "groupId"
+]
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

With destructiveHint=true already in annotations, the description still adds the ⚠️ Destructive warning, the confirmation guard, and the body-vs-path placement detail. This provides useful behavioral context beyond what annotations and schema alone convey.

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 two compact sentences with no filler. The destructive warning and core action are front-loaded, followed by the API-specific placement detail and the confirm requirement.

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 destructive operation with annotations present and no output schema, the description covers the action, warning, required confirmation flag, and parameter placement. It relies on the schema for groupId and the policyId/policyIdList choice, which is acceptable since schema coverage is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, giving a baseline of 3. The description adds meaning by explaining that policy IDs are transmitted via policyIdList in the request body and that no policy ID belongs in the path, complementing the schema's per-parameter descriptions.

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 states a specific action ('Remove one or more IAM policies from a group') with a clear verb and resource. It distinguishes this tool from close siblings like attach_policy_to_group and detach_policy_from_sub_account by naming the target resource ('group').

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 clarifies the key execution requirement (set confirm=true) and an API nuance (policy IDs go in the body as policyIdList, not in the path). It does not explicitly name alternative sibling tools or when-not-to-use conditions, but the verb and resource make the primary use case clear.

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