IBM Cloud MCP Server

iam_delete_access_group

Delete an access group by specifying its ID, removing associated policies and members.

Instructions

Delete an access group

Input Schema

TableJSON Schema

Name	Required	Description	Default
`access_group_id`	Yes	ID of the access group to delete

Implementation Reference

src/tools/iam/index.ts:188-200 (handler)

The handler function that executes the iam_delete_access_group tool logic. It deletes an access group by its ID via a DELETE request to the IAM Access Groups API.

// ─── iam_delete_access_group ──────────────────────────────────
server.tool(
  "iam_delete_access_group",
  "Delete an access group",
  {
    access_group_id: z.string().describe("ID of the access group to delete"),
  },
  async ({ access_group_id }) => safeTool(async () => {
    assertWriteAllowed(config.allowWrite);
    await client.delete(`${IBM_ENDPOINTS.IAM_ACCESS_GROUPS}/groups/${access_group_id}`);
    return { message: `Access group ${access_group_id} deleted successfully` };
  })
);

src/tools/iam/index.ts:192-193 (schema)
Input schema for the tool: requires a single string parameter 'access_group_id' which is the ID of the access group to delete.
```
{
  access_group_id: z.string().describe("ID of the access group to delete"),
```

src/tools/iam/index.ts:189-200 (registration)

Registration of 'iam_delete_access_group' as a tool on the MCP server instance, within the registerIAMTools function.

server.tool(
  "iam_delete_access_group",
  "Delete an access group",
  {
    access_group_id: z.string().describe("ID of the access group to delete"),
  },
  async ({ access_group_id }) => safeTool(async () => {
    assertWriteAllowed(config.allowWrite);
    await client.delete(`${IBM_ENDPOINTS.IAM_ACCESS_GROUPS}/groups/${access_group_id}`);
    return { message: `Access group ${access_group_id} deleted successfully` };
  })
);

src/server.ts:50-50 (registration)
The registerIAMTools function is called here during server initialization, which registers the iam_delete_access_group tool.
```
registerIAMTools(server, client, config);
```
src/config.ts:29-29 (helper)
Definition of the IAM_ACCESS_GROUPS endpoint URL used by the tool to make the DELETE request.
```
IAM_ACCESS_GROUPS: "https://iam.cloud.ibm.com/v2",
```

Tool Definition Quality

C2.8/5.0

Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Delete', failing to mention that deletion is destructive, irreversible, or may require removing members or policies first. Critical safety information is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (3 words), but it lacks necessary detail. It is not verbose, but the brevity comes at the cost of missing critical information. Acceptable for a simple tool but could be improved.

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

Completeness2/5

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

For a destructive tool with no output schema, the description should explain return values (e.g., success confirmation), side effects, and dependencies. It only states the action, leaving the agent without enough context to use it safely.

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%, and the parameter is described in the schema. The description adds no additional parameter context beyond what the schema provides, meeting the baseline of 3.

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 'Delete an access group' clearly states the action and resource. It distinguishes itself from sibling tools like iam_create_access_group and iam_list_access_groups by specifying deletion.

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?

No guidance is provided on when to use this tool, prerequisites (e.g., whether the group must be empty), or consequences. There is no mention of alternatives or post-deletion effects.

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

Install Server

Other Tools

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ahmedselimmansor-ctrl/IBM_cloud_MCP_SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server