Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

schematics_list_actions

List all available Schematics actions to manage infrastructure as code on IBM Cloud.

Instructions

List Schematics actions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The handler for the schematics_list_actions tool. It makes a GET request to the Schematics V2 API /actions endpoint with an optional limit parameter, defaulting to 100.
    server.tool("schematics_list_actions", "List Schematics actions", {
      limit: z.number().optional(),
    }, async (p) => safeTool(() => client.get(`${baseV2}/actions`, {limit:p.limit||100})));
  • Input schema for schematics_list_actions: accepts an optional 'limit' number parameter.
    server.tool("schematics_list_actions", "List Schematics actions", {
      limit: z.number().optional(),
    }, async (p) => safeTool(() => client.get(`${baseV2}/actions`, {limit:p.limit||100})));
  • Registration function registerSchematicsTools is exported and called from src/server.ts. The tool is registered via server.tool() within this function.
    export function registerSchematicsTools(server: McpServer, client: IBMCloudAPIClient, config: ServerConfig) {
      const base = IBM_ENDPOINTS.SCHEMATICS(config.region);
      const baseV2 = IBM_ENDPOINTS.SCHEMATICS_V2(config.region);
      const w = () => assertWriteAllowed(config.allowWrite);
    
      server.tool("schematics_list_workspaces", "List Schematics workspaces", {
        limit: z.number().optional(),
      }, async (p) => safeTool(() => client.get(`${base}/workspaces`, {limit:p.limit||100})));
    
      server.tool("schematics_get_workspace", "Get workspace details", {
        workspace_id: z.string(),
      }, async (p) => safeTool(() => client.get(`${base}/workspaces/${p.workspace_id}`)));
    
      server.tool("schematics_create_workspace", "Create a Schematics workspace", {
        name: z.string(), description: z.string().optional(),
        template_repo_url: z.string().describe("Git repo URL with Terraform configs"),
        resource_group: z.string().optional(), terraform_version: z.string().optional(),
      }, async (p) => safeTool(async () => { w();
        return client.post(`${base}/workspaces`, {
          name:p.name, description:p.description, resource_group:p.resource_group,
          template_repo:{url:p.template_repo_url},
          type:[p.terraform_version||"terraform_v1.5"],
        });
      }));
    
      server.tool("schematics_delete_workspace", "Delete a Schematics workspace", {
        workspace_id: z.string(), destroy_resources: z.boolean().optional(),
      }, async (p) => safeTool(async () => { w();
        await client.delete(`${base}/workspaces/${p.workspace_id}`, {destroy_resources:p.destroy_resources?"true":undefined});
        return {message:"Workspace deleted"};
      }));
    
      server.tool("schematics_plan_workspace", "Generate a Terraform plan for a workspace", {
        workspace_id: z.string(),
      }, async (p) => safeTool(async () => { w();
        return client.post(`${base}/workspaces/${p.workspace_id}/plan`, {});
      }));
    
      server.tool("schematics_apply_workspace", "Apply Terraform plan for a workspace", {
        workspace_id: z.string(),
      }, async (p) => safeTool(async () => { w();
        return client.put(`${base}/workspaces/${p.workspace_id}/apply`, {});
      }));
    
      server.tool("schematics_list_actions", "List Schematics actions", {
        limit: z.number().optional(),
      }, async (p) => safeTool(() => client.get(`${baseV2}/actions`, {limit:p.limit||100})));
    
      server.tool("schematics_get_job", "Get Schematics job details", {
        job_id: z.string(),
      }, async (p) => safeTool(() => client.get(`${baseV2}/jobs/${p.job_id}`)));
    }
  • src/server.ts:83-84 (registration)
    The schematics_list_actions tool is registered as part of the Schematics tool group when createServer() is called.
    registerSchematicsTools(server, client, config);
    console.error(`  ✓ Schematics (8 tools)`);
  • The safeTool helper wraps the handler to catch errors and return proper MCP success/error responses.
    export async function safeTool<T>(fn: () => Promise<T>): Promise<ReturnType<typeof successContent> | ReturnType<typeof errorContent>> {
      try {
        const result = await fn();
        return successContent(result);
      } catch (error) {
        return errorContent(error);
      }
    }
Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits such as read-only nature, authentication requirements, rate limits, or output characteristics. The description carries full burden but is silent.

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

Conciseness2/5

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

The description is one short phrase, which is under-specified rather than concise. It lacks essential details and is not front-loaded with informative content.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is incomplete. It does not explain what actions are listed, the format, or the effect of the limit parameter.

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

Parameters1/5

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

The only parameter 'limit' is not described. With 0% schema description coverage, the description adds no meaning beyond the schema, which only specifies type 'number'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'List Schematics actions' is vague. It does not specify what 'actions' refers to (e.g., workspace actions, job actions). Among siblings like schematics_apply_workspace and schematics_create_workspace, the tool's purpose is unclear.

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. The description does not mention that it might be used to discover available actions before invoking specific ones.

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