Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

ce_update_app

Update an IBM Cloud Code Engine application by modifying its image, port, or scaling settings.

Instructions

Update a Code Engine application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
app_nameYes
image_referenceNo
image_portNo
scale_minNo
scale_maxNo
regionNo

Implementation Reference

  • The handler function for ce_update_app. It builds a body object with optional fields (image_reference, image_port, scale_min/max) and sends a PATCH request to the Code Engine API to update an application.
    server.tool("ce_update_app", "Update a Code Engine application", {
      project_id: z.string(), app_name: z.string(),
      image_reference: z.string().optional(), image_port: z.number().optional(),
      scale_min: z.number().optional(), scale_max: z.number().optional(),
      region: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      const body: Record<string,unknown> = {};
      if(p.image_reference) body.image_reference=p.image_reference;
      if(p.image_port) body.image_port=p.image_port;
      if(p.scale_min!==undefined) body.scale_min_instances=p.scale_min;
      if(p.scale_max!==undefined) body.scale_max_instances=p.scale_max;
      return client.patch(`${base(p.region||r)}/projects/${p.project_id}/apps/${p.app_name}`, body);
    }));
  • Zod schema defining input parameters: project_id (required string), app_name (required string), image_reference (optional string), image_port (optional number), scale_min (optional number), scale_max (optional number), region (optional string).
    project_id: z.string(), app_name: z.string(),
    image_reference: z.string().optional(), image_port: z.number().optional(),
    scale_min: z.number().optional(), scale_max: z.number().optional(),
    region: z.string().optional(),
  • The export function registerCodeEngineTools that contains the server.tool registration for ce_update_app (and all other Code Engine tools).
    export function registerCodeEngineTools(server: McpServer, client: IBMCloudAPIClient, config: ServerConfig) {
  • src/server.ts:62-62 (registration)
    Call to registerCodeEngineTools in the main server setup, which registers the ce_update_app tool among others.
    registerCodeEngineTools(server, client, config);
Behavior2/5

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

No annotations exist. The description only says 'update', which implies mutation, but does not disclose whether it's a partial update, full replacement, or if it triggers a restart. No behavioral details beyond the verb.

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 structure. It could be expanded with bullet points or additional context while remaining concise.

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?

With 7 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain required fields, effect of update, error scenarios, or return values.

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 adds no explanation for any of the 7 parameters. The agent must infer meaning from parameter names alone, which is insufficient.

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

Purpose4/5

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

The description clearly states the action (update) and the resource (Code Engine application). It distinguishes from create and delete siblings, but could be more specific about what properties can be updated.

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 like ce_create_app or ce_list_apps. No prerequisites or context provided.

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