Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ce_delete_app

Delete a Code Engine application by providing the project ID and app name.

Instructions

Delete a Code Engine application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
app_nameYes
regionNo

Implementation Reference

  • The handler function for the 'ce_delete_app' tool. It takes project_id, app_name, and optional region, checks write permission, makes a DELETE API call to the Code Engine API to delete the app, and returns a success message.
    server.tool("ce_delete_app", "Delete a Code Engine application", {
      project_id: z.string(), app_name: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${base(p.region||r)}/projects/${p.project_id}/apps/${p.app_name}`);
      return {message:"App deleted"};
    }));
  • Input schema for ce_delete_app: requires project_id (string), app_name (string), and optional region (string).
    project_id: z.string(), app_name: z.string(), region: z.string().optional(),
  • Tool registration via server.tool('ce_delete_app', ...) inside registerCodeEngineTools function.
    server.tool("ce_delete_app", "Delete a Code Engine application", {
      project_id: z.string(), app_name: z.string(), region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      await client.delete(`${base(p.region||r)}/projects/${p.project_id}/apps/${p.app_name}`);
      return {message:"App deleted"};
    }));
  • src/server.ts:62-63 (registration)
    registerCodeEngineTools is called from createServer in server.ts, which registers all Code Engine tools including ce_delete_app.
    registerCodeEngineTools(server, client, config);
    console.error(`  ✓ Code Engine (16 tools)`);
  • The client.delete method used by the handler to issue the HTTP DELETE request to the Code Engine API.
    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?

No annotations provided, so description carries full burden. It does not disclose destructive nature, failure conditions, or cascading effects. The description is too minimal.

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 very short (5 words) and to the point, but lacks structure and could benefit from additional context while remaining concise.

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 no output schema and minimal description, the tool is under-documented. Missing details on success behavior, errors, and prerequisites.

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% and description does not explain any of the three parameters (project_id, app_name, region). Their meanings are implied by names but not clarified.

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 verb 'Delete' and the resource 'Code Engine application', distinguishing it from siblings like ce_create_app and ce_list_apps. The name also encodes 'delete'.

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 vs. alternatives (e.g., ce_delete_job) or prerequisites. The description lacks context about required project or app state.

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