Skip to main content
Glama
ahmedselimmansor-ctrl

Alibaba Cloud MCP Server

slb_list

List Server Load Balancer (SLB) instances in a specified Alibaba Cloud region by providing the region ID.

Instructions

List Server Load Balancers (SLB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdNo

Implementation Reference

  • Registration of the 'slb_list' tool, returning the tool metadata including its name, description, and input schema (regionId). Registered in src/index.ts via registerSlbTools().
    export function registerSlbTools() {
      return [
        {
          name: "slb_list",
          description: "List Server Load Balancers (SLB).",
          inputSchema: {
            type: "object",
            properties: {
              regionId: { type: "string" }
            }
          }
        }
      ];
    }
  • Handler for 'slb_list'. Creates an SLB API client, parses args with Zod (regionId defaults to config region), then calls DescribeLoadBalancers API via POST and returns the result as text JSON content.
    export async function handleSlbTools(name: string, args: any) {
      // @ts-ignore
      const client = new Core.default({
        accessKeyId: config.ALIBABA_CLOUD_ACCESS_KEY_ID,
        accessKeySecret: config.ALIBABA_CLOUD_ACCESS_KEY_SECRET,
        endpoint: 'https://slb.aliyuncs.com',
        apiVersion: '2014-05-15',
      });
    
      if (name === "slb_list") {
        const parsed = z.object({
          regionId: z.string().default(config.ALIBABA_CLOUD_REGION_ID)
        }).parse(args);
    
        return { content: [{ type: "text", text: JSON.stringify(await client.request('DescribeLoadBalancers', { RegionId: parsed.regionId }, { method: 'POST' }), null, 2) }] };
      }
    
      throw new Error(`Unknown SLB tool: ${name}`);
    }
  • Input schema for 'slb_list' tool: a JSON object with an optional regionId string property.
    inputSchema: {
      type: "object",
      properties: {
        regionId: { type: "string" }
      }
    }
  • src/index.ts:16-16 (registration)
    Import and registration of registerSlbTools and handleSlbTools in the main server file.
    import { registerSlbTools, handleSlbTools } from "./tools/slb/index.js";
  • Routing for slb_* tools: calls handleSlbTools when tool name starts with 'slb_'.
    if (name.startsWith("slb_")) {
      return await handleSlbTools(name, args);
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It merely states 'List' without mentioning safety, permissions, side effects, or limits such as pagination or default scope.

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 very short and front-loaded, which is good for quick scanning. However, it is too minimal; it could include region filtering information without adding much length.

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?

Given the tool has one optional parameter, no output schema, and no annotations, the description fails to explain the region parameter, return format, default behavior (list all or paginated), or any constraints. It is severely incomplete.

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?

The input schema has one parameter (regionId) with 0% schema description coverage. The description does not mention this parameter or its purpose (filtering by region), leaving the agent without guidance on a critical aspect of usage.

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 ('List') and the resource ('Server Load Balancers'), making the tool's purpose immediately understandable. However, it could be more specific by mentioning the optional region filtering, which would differentiate it from other list tools.

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 ecs_list_instances or ack_list_clusters. The agent has no context for selecting this over similar list operations.

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/Alibaba_cloud_MCP_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server