Skip to main content
Glama
ahmedselimmansor-ctrl

Alibaba Cloud MCP Server

ram_list_users

List all IAM users in your Alibaba Cloud account.

Instructions

List IAM/RAM users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:63-65 (registration)
    The ram_list_users tool routing: when tool name starts with 'ram_', it is dispatched to handleRamTools().
    if (name.startsWith("ram_")) {
      return await handleRamTools(name, args);
    }
  • Registration of ram_list_users tool with name, description, and empty inputSchema (no parameters).
    export function registerRamTools() {
      return [
        {
          name: "ram_list_users",
          description: "List IAM/RAM users.",
          inputSchema: {
            type: "object",
            properties: {}
          }
        }
      ];
    }
  • Handler function that executes ram_list_users by calling Alibaba Cloud RAM ListUsers API and returning the result as JSON text.
    export async function handleRamTools(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://ram.aliyuncs.com',
        apiVersion: '2015-05-01',
      });
    
      if (name === "ram_list_users") {
        return { content: [{ type: "text", text: JSON.stringify(await client.request('ListUsers', {}, { method: 'POST' }), null, 2) }] };
      }
    
      throw new Error(`Unknown RAM tool: ${name}`);
    }
  • src/index.ts:38-38 (registration)
    registerRamTools() is called during ListTools request to expose ram_list_users in the tool list.
    ...registerRamTools(),
  • Auth config providing ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET used by the RAM handler.
    import dotenv from 'dotenv';
    import { z } from 'zod';
    
    dotenv.config();
    
    const configSchema = z.object({
      ALIBABA_CLOUD_ACCESS_KEY_ID: z.string().min(1, "Access Key ID is required"),
      ALIBABA_CLOUD_ACCESS_KEY_SECRET: z.string().min(1, "Access Key Secret is required"),
      ALIBABA_CLOUD_REGION_ID: z.string().default("cn-hangzhou"),
    });
    
    export const config = configSchema.parse(process.env);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that it lists users, but does not mention any side effects, permissions needed, pagination, or other behavioral traits. This is insufficient for an agent to understand potential consequences.

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

Conciseness4/5

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

The description is a single concise sentence that directly states the tool's purpose. It is front-loaded and efficient, though it could potentially include more detail without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema), the description is minimally sufficient. However, it lacks context about the output format or any filtering capabilities, which could be helpful for an agent. It is adequate but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4. The description adds no parameter-specific meaning beyond the empty schema, but this is acceptable as there are no parameters to describe.

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 clearly states the action ('List') and the resource ('IAM/RAM users'), which distinguishes it from sibling tools like ecs_list_instances or rds_list_instances. The verb+resource combination is specific and unambiguous.

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 is provided on when to use this tool versus alternatives. The description does not include any context about prerequisites, limitations, or scenarios where other tools would be more 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/Alibaba_cloud_MCP_server'

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