Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ks_enable_addon

Enable a specified add-on for a Kubernetes cluster to extend its functionality, solving the need for additional services.

Instructions

Enable a cluster add-on

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clusterYes
addon_nameYes

Implementation Reference

  • Tool 'ks_enable_addon' is registered via server.tool() with schema for 'cluster' and 'addon_name' parameters and a handler that calls client.patch to enable the addon.
    server.tool("ks_enable_addon", "Enable a cluster add-on", {
      cluster: z.string(), addon_name: z.string(),
    }, async (p) => safeTool(async () => { w();
      return client.patch(`${base}/v1/clusters/${p.cluster}/addons`, {[p.addon_name]:{enabled:true}});
    }));
  • The handler function (async (p) => ...) executes the tool logic: calls assertWriteAllowed via the w() helper, then sends a PATCH request to enable the addon on the given cluster.
    server.tool("ks_enable_addon", "Enable a cluster add-on", {
      cluster: z.string(), addon_name: z.string(),
    }, async (p) => safeTool(async () => { w();
      return client.patch(`${base}/v1/clusters/${p.cluster}/addons`, {[p.addon_name]:{enabled:true}});
    }));
  • Input schema: 'cluster' (z.string()) and 'addon_name' (z.string()) are validated using Zod.
    server.tool("ks_enable_addon", "Enable a cluster add-on", {
      cluster: z.string(), addon_name: z.string(),
  • assertWriteAllowed helper: called at the start of the handler via w() to ensure write operations are permitted.
    export function assertWriteAllowed(allowWrite: boolean): void {
      if (!allowWrite) {
        throw new WriteNotAllowedError();
      }
  • client.patch helper: the HTTP PATCH method used to send the enable request to the IBM Cloud Kubernetes API.
    async patch<T = unknown>(url: string, body?: unknown, queryParams?: Record<string, string | number | boolean | undefined>): Promise<T> {
      return this.request<T>(url, { method: "PATCH", body, queryParams });
    }
    
    async delete<T = unknown>(url: string, queryParams?: Record<string, string | number | boolean | undefined>): Promise<T> {
      return this.request<T>(url, { method: "DELETE", queryParams });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure. It only says 'Enable', omitting effects like idempotency, what happens if already enabled, or required permissions/state.

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 a single sentence, minimal but not overly verbose. However, the brevity sacrifices informative content that could be added without harming conciseness.

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?

Despite the tool's simplicity, the description lacks context about prerequisites, side effects, or whether the operation is reversible. It fails to provide sufficient information for an agent to use it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the schema provides no parameter descriptions. The tool description also does not explain what 'cluster' or 'addon_name' represent, leaving the agent to rely solely on parameter names.

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 action ('Enable') and the resource ('a cluster add-on'), distinguishing it from sibling tools like ks_disable_addon and ks_list_addons.

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 on when to use this tool versus alternatives (e.g., ks_list_addons to check status) or prerequisites. The agent must infer usage from the name alone.

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

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