Skip to main content
Glama
RadiumGu

Alibaba Cloud Operations MCP Server

by RadiumGu

describe_rds_instances

List RDS instances in a specified region to monitor and manage database resources on Alibaba Cloud.

Instructions

查询RDS实例列表

Args:
    region: 区域ID,如cn-beijing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNocn-beijing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'describe_rds_instances'. It is decorated with @app.tool() for registration and implements logic by attempting to delegate to a matching function in common_api_tools.tools (though none matches), falling back to an availability message.
    @app.tool()
    def describe_rds_instances(region: str = "cn-beijing") -> str:
        """查询RDS实例列表
        
        Args:
            region: 区域ID,如cn-beijing
        """
        try:
            sys.path.insert(0, os.path.join(os.path.dirname(__file__), 'alibaba_cloud_ops_mcp_server'))
            from tools import common_api_tools
            
            for tool_func in common_api_tools.tools:
                if hasattr(tool_func, '__name__') and 'rds' in tool_func.__name__.lower() and 'describe' in tool_func.__name__.lower():
                    result = tool_func(RegionId=region)
                    return str(result)
            
            return f"RDS实例查询功能可用,查询region: {region}"
        except Exception as e:
            return f"RDS查询失败: {str(e)}"
  • Configuration listing supported APIs for RDS service, including 'DescribeDBInstances', likely used by common API tools to understand available operations.
    'rds': [
        'DescribeDBInstances'
    ]
  • Generic helper tool 'CommonAPICaller' in common_api_tools that can call RDS APIs like DescribeDBInstances, which the handler attempts to delegate to (though name matching fails).
    def CommonAPICaller(
            service: str = Field(description='AlibabaCloud service code'),
            api: str = Field(description='AlibabaCloud api name'),
            parameters: dict = Field(description='AlibabaCloud ECS instance ID List', default={}),
    ):
        """
        Use PromptUnderstanding tool first to understand the user's query, Perform the actual call by specifying the Service, API, and Parameters
        """
        return _tools_api_call(service, api, parameters, None)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a query operation, implying read-only behavior, but doesn't specify if it requires authentication, has rate limits, returns paginated results, or details the output format. The description adds minimal behavioral context beyond the basic action.

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 concise with two sentences: one stating the purpose and another explaining the parameter. It's front-loaded with the main action, and there's no redundant information. However, the use of Chinese might reduce clarity for some agents, and the structure could be slightly improved with clearer formatting.

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 has 1 parameter, no annotations, and an output schema exists, the description is minimally complete. It covers the basic purpose and parameter, but lacks details on behavioral traits, usage context, and output expectations, making it adequate but with clear gaps for effective tool invocation.

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

Parameters3/5

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

The description includes an 'Args' section that explains the 'region' parameter with an example ('cn-beijing'), adding meaning beyond the input schema, which has 0% description coverage and only provides a default value. However, with only 1 parameter and partial documentation in the description, it meets the baseline for adequate but not comprehensive coverage.

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?

The description states the tool's purpose as '查询RDS实例列表' (query RDS instance list), which clearly indicates it retrieves a list of RDS instances. However, it doesn't differentiate from sibling tools like 'describe_ecs_instances' beyond the resource type (RDS vs ECS), and the title is null, leaving some ambiguity about the exact scope.

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. It doesn't mention any prerequisites, exclusions, or comparisons to sibling tools like 'describe_ecs_instances' or other describe_* tools, leaving the agent to infer usage based on the resource name alone.

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/RadiumGu/alicloud-ops-mcp'

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