Skip to main content
Glama
ahmedselimmansor-ctrl

Alibaba Cloud MCP Server

rds_list_instances

Retrieve a list of RDS instances in your Alibaba Cloud account, optionally filtered by region.

Instructions

List RDS instances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdNo

Implementation Reference

  • The handleRdsTools function handles 'rds_list_instances' by creating an Alibaba Cloud RDS client and calling DescribeDBInstances API with the provided regionId (defaulting to config region). Returns JSON-stringified list of instances.
    export async function handleRdsTools(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://rds.aliyuncs.com',
        apiVersion: '2014-08-15',
      });
    
      if (name === "rds_list_instances") {
        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('DescribeDBInstances', { RegionId: parsed.regionId }, { method: 'POST' }), null, 2) }] };
      }
    
      throw new Error(`Unknown RDS tool: ${name}`);
    }
  • registerRdsTools defines the input schema for 'rds_list_instances': an object with an optional 'regionId' string property.
    export function registerRdsTools() {
      return [
        {
          name: "rds_list_instances",
          description: "List RDS instances.",
          inputSchema: {
            type: "object",
            properties: {
              regionId: { type: "string" }
            }
          }
        }
      ];
    }
  • src/index.ts:31-43 (registration)
    The server registers the tool via ListToolsRequestSchema handler, spreading registerRdsTools() into the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...registerUniversalTool(),
          ...registerEcsTools(),
          ...registerVpcTools(),
          ...registerRdsTools(),
          ...registerRamTools(),
          ...registerAckTools(),
          ...registerSlbTools()
        ],
      };
    });
  • src/index.ts:60-62 (registration)
    The CallToolRequestSchema handler routes tool calls starting with 'rds_' to handleRdsTools().
    if (name.startsWith("rds_")) {
      return await handleRdsTools(name, args);
    }
Behavior2/5

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

With no annotations, the description must disclose behaviors itself. It only states it lists instances but lacks information on permissions, side effects, rate limits, or pagination. The read-only nature is implicit but not confirmed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no unnecessary words. It is maximally concise, though this brevity may sacrifice 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?

Given the simplicity (1 parameter, no output schema), the description is minimally adequate but omits critical context like output format, pagination details, or any filtering capabilities. It lacks completeness for effective use.

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 single parameter regionId has no description in the schema (coverage 0%) and is not explained in the tool description. The description adds no meaning 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?

The description 'List RDS instances' is clear and specific: it identifies the verb 'List' and the resource 'RDS instances', which distinguishes it from sibling tools like ecs_list_instances or ack_list_clusters.

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?

The description provides no guidance on when to use this tool versus alternatives, such as ecs_list_instances. There is no mention of prerequisites, context, or when not to use it.

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