Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

cf_start_app

Starts a Cloud Foundry application using its app GUID, enabling prompt activation of cloud apps.

Instructions

Start a Cloud Foundry application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_guidYes

Implementation Reference

  • The handler for the 'cf_start_app' tool. It calls assertWriteAllowed to check write permissions, then POSTs to the CF v3 apps actions/start endpoint.
    server.tool("cf_start_app", "Start a Cloud Foundry application", {
      app_guid: z.string(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${base}/v3/apps/${p.app_guid}/actions/start`, {});
    }));
  • Input schema for cf_start_app: requires 'app_guid' as a string (Zod validation).
    server.tool("cf_start_app", "Start a Cloud Foundry application", {
      app_guid: z.string(),
    }, async (p) => safeTool(async () => { w();
  • Registration of the 'cf_start_app' tool via server.tool() inside registerCloudFoundryTools().
    server.tool("cf_start_app", "Start a Cloud Foundry application", {
      app_guid: z.string(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${base}/v3/apps/${p.app_guid}/actions/start`, {});
    }));
  • src/server.ts:89-89 (registration)
    Top-level registration: registerCloudFoundryTools is called from createServer() to register all CF tools including cf_start_app.
    registerCloudFoundryTools(server, client, config);
  • assertWriteAllowed helper used by the handler to guard write operations when allowWrite is false.
    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?

No annotations provided. Description only says 'Start' but omits side effects, state changes, or error conditions. For a mutation tool, this is insufficient.

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?

Extremely concise (5 words), but at the cost of missing critical details. Structure is minimal.

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 lack of annotations, output schema, and schema descriptions, the description fails to provide enough context for correct invocation. Missing what happens on success, errors, or constraints.

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 has 0% description coverage and description does not explain the meaning of app_guid or how to obtain it. No added value beyond the parameter name.

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?

Description clearly states action and resource: 'Start a Cloud Foundry application'. It distinguishes from sibling tools like cf_stop_app.

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 when-to-use or when-not-to-use guidance. Lacks context like prerequisites (e.g., app must be stopped) or comparison to alternatives.

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