Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

watson_list_models

Lists foundation models available on watsonx.ai.

Instructions

List available foundation models on watsonx.ai

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNo

Implementation Reference

  • The handler function for the 'watson_list_models' tool. It makes a GET request to the watsonx.ai ML API endpoint for foundation model specs, with an optional region parameter and version/limit query params.
    server.tool("watson_list_models", "List available foundation models on watsonx.ai", {
      region: z.string().optional(),
    }, async (p) => safeTool(() => client.get(`${ml(p.region||r)}/ml/v1/foundation_model_specs`, {version:ver,limit:200})));
  • Input schema for 'watson_list_models': an optional 'region' string parameter (Zod schema).
    region: z.string().optional(),
  • src/server.ts:68-69 (registration)
    Registration call: registerWatsonTools(server, client, config) which registers the 'watson_list_models' tool along with other Watson tools.
    registerWatsonTools(server, client, config);
    console.error(`  ✓ Watson AI (8 tools)`);
  • The registerWatsonTools function definition that registers all Watson tools including 'watson_list_models' via server.tool().
    export function registerWatsonTools(server: McpServer, client: IBMCloudAPIClient, config: ServerConfig) {
  • The IBM_ENDPOINTS.WATSON_ML helper that constructs the watsonx.ai ML API base URL (https://{region}.ml.cloud.ibm.com).
    WATSON_ML: (region: string) =>
      `https://${region}.ml.cloud.ibm.com`,
Behavior2/5

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

No annotations provided. Description only states 'list' without disclosing read-only nature, permissions required, pagination, or whether the region parameter filters results. Agent lacks behavioral insight 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?

Single sentence is concise but overly brief. Lacks details that could be added without verbosity, such as listing return format or parameter usage. Adequate for a trivial tool but not earning high marks.

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 exists, so description should explain return value. Does not indicate whether result is a list of names or detailed objects. Incomplete for a tool with one parameter and no annotations.

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 one parameter 'region' with no description (coverage 0%). Description does not mention or explain the parameter, leaving the agent to guess its purpose and effect.

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 'List available foundation models on watsonx.ai', specifying the verb 'list' and resource 'foundation models'. It distinguishes from siblings like watson_get_model or watson_deploy_model by focusing on listing. However, it could be more specific about what metadata is returned.

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 like watson_get_model or watson_deploy_model. Does not mention prerequisites, context, or situations where listing is appropriate.

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