Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ce_create_project

Creates an IBM Cloud Code Engine project. Specify a name, resource group, and region to set up a new project.

Instructions

Create a Code Engine project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
resource_group_idNo
regionNo

Implementation Reference

  • Registration of the 'ce_create_project' tool via server.tool(), defining its schema and handler inline.
    server.tool("ce_create_project", "Create a Code Engine project", {
      name: z.string(), resource_group_id: z.string().optional(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${base(p.region||r)}/projects`, {name:p.name,resource_group_id:p.resource_group_id});
    }));
  • Handler function that calls assertWriteAllowed (write guard) then posts to the Code Engine projects API endpoint with name and optional resource_group_id.
    }, async (p) => safeTool(async () => { w();
      return client.post(`${base(p.region||r)}/projects`, {name:p.name,resource_group_id:p.resource_group_id});
    }));
  • Zod schema defining input parameters: name (required string), resource_group_id (optional string), region (optional string).
    name: z.string(), resource_group_id: z.string().optional(), region: z.string().optional(),
  • The safeTool wrapper that catches errors and formats success/error MCP responses used by the handler.
    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);
      }
    }
  • The assertWriteAllowed helper that checks if write operations are permitted before executing the POST request.
    export function assertWriteAllowed(allowWrite: boolean): void {
      if (!allowWrite) {
        throw new WriteNotAllowedError();
      }
    }
Behavior2/5

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

With no annotations, the description should fully disclose behavior. It only states the action without mentioning side effects, authentication needs, or whether the operation is destructive. Minimal value beyond the tool name.

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, which is concise but lacks necessary details. It prioritizes brevity over completeness, resulting in an under-specified definition.

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

Completeness1/5

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

Given the tool's complexity (creation with 3 parameters, no output schema), the description is severely incomplete. It omits return values, error cases, prerequisites, and any contextual information needed for correct usage.

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?

Schema description coverage is 0%, and the description does not explain any parameter meaning or constraints. The agent has no guidance on what 'resource_group_id' or 'region' represent or how to format them.

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 'Create a Code Engine project', using a specific verb and resource. It distinguishes itself from sibling tools like ce_create_app or ce_create_build, which create different Code Engine resources.

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?

No explicit guidance on when to use vs alternatives, but the name alone implies its use for project creation. However, given multiple creation tools in the same domain, more context would help differentiate use cases.

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