Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

cf_get_app

Retrieves details for a Cloud Foundry application by providing its app GUID.

Instructions

Get Cloud Foundry application details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_guidYes

Implementation Reference

  • The handler function for 'cf_get_app'. It executes an HTTP GET request to the IBM Cloud Foundry API endpoint /v3/apps/{app_guid} using the client's get() method, wrapped in safeTool() for error handling.
    server.tool("cf_get_app", "Get Cloud Foundry application details", {
      app_guid: z.string(),
    }, async (p) => safeTool(() => client.get(`${base}/v3/apps/${p.app_guid}`)));
  • The input schema for 'cf_get_app'. It defines a single required parameter 'app_guid' of type string (Zod schema) for specifying the Cloud Foundry application GUID.
    server.tool("cf_get_app", "Get Cloud Foundry application details", {
      app_guid: z.string(),
    }, async (p) => safeTool(() => client.get(`${base}/v3/apps/${p.app_guid}`)));
  • Registration of 'cf_get_app' tool via server.tool() with name 'cf_get_app', description 'Get Cloud Foundry application details', and the schema + handler.
    server.tool("cf_get_app", "Get Cloud Foundry application details", {
      app_guid: z.string(),
    }, async (p) => safeTool(() => client.get(`${base}/v3/apps/${p.app_guid}`)));
  • The registerCloudFoundryTools function is exported and invoked from src/server.ts (line 89) to register all Cloud Foundry tools including 'cf_get_app'.
    export function registerCloudFoundryTools(server: McpServer, client: IBMCloudAPIClient, config: ServerConfig) {
  • The safeTool() helper wraps the handler's async function, catching errors and formatting responses as MCP text content blocks.
    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);
      }
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, permissions, or side effects. 'Get' implies reading but is not explicit.

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?

Single sentence is concise, but it omits necessary detail. It is front-loaded but could be more informative without losing conciseness.

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 simplicity of the tool (one param, no output schema), the description is insufficient. It does not describe return values or provide context for using the tool effectively.

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?

The single parameter 'app_guid' lacks description in the schema and the tool description does not explain what it represents. Schema coverage is 0%, and the description adds no value.

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?

Description clearly states the tool gets Cloud Foundry application details, distinguishing it from sibling tools like cf_start_app or cf_list_apps. However, 'details' is somewhat vague.

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 cf_list_apps or other app-related tools. The description lacks context for selection.

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