Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

vpc_list_images

List available OS images for provisioning VPC instances. Filter by visibility (public/private) or region.

Instructions

List available OS images

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
visibilityNo
regionNo

Implementation Reference

  • Registration of the vpc_list_images tool with schema params (limit, visibility, region) and handler calling GET /images via the API client.
    server.tool("vpc_list_images", "List available OS images", {
      limit: z.number().optional(), visibility: z.enum(["public","private"]).optional(), region: z.string().optional(),
    }, async (p) => safeTool(() => client.get(vpcUrl(p.region||r, "/images"), {limit:p.limit,visibility:p.visibility})));
  • The handler function for vpc_list_images. It calls client.get with the VPC API URL for /images, passing optional limit and visibility query params, wrapped in safeTool for error handling.
    }, async (p) => safeTool(() => client.get(vpcUrl(p.region||r, "/images"), {limit:p.limit,visibility:p.visibility})));
  • Input schema for vpc_list_images: optional limit (number), visibility (enum: public/private), and region (string).
    limit: z.number().optional(), visibility: z.enum(["public","private"]).optional(), region: z.string().optional(),
  • Helper function that builds the full VPC API URL with region, path, version, and generation=2 parameters.
    export function vpcUrl(region: string, path: string, version: string = "2024-11-19"): string {
      const base = `https://${region}.iaas.cloud.ibm.com/v1${path}`;
      const sep = base.includes("?") ? "&" : "?";
      return `${base}${sep}version=${version}&generation=2`;
    }
  • Wrapper that executes the handler function and catches errors, returning either success or error formatted MCP responses.
    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 are provided, and the description does not disclose any behavioral traits such as pagination, rate limits, or authorization requirements. The term 'available' is ambiguous.

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?

Very concise (4 words), but lacks necessary detail. Conciseness is positive but comes at the cost of completeness.

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?

No output schema, so return format is unknown. With three parameters, the description should provide more context on how they interact, but it does not.

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?

Input schema has 0% description coverage, and the tool description adds no information about the parameters (limit, visibility, region). Schema enums are present but unexplained.

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

Purpose3/5

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

Description states 'List available OS images' which is a clear verb+resource, but it does not differentiate from sibling tools like cr_list_images or provide any scope. It is adequate but not distinctive.

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, prerequisites, or context for invocation. Missing information like whether region is required or how visibility affects results.

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