Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

modify_security_ips

Update the IP whitelist for an Alibaba Cloud RDS instance to control database access by specifying allowed IP addresses and network types.

Instructions

modify security ips。

Args:
    region_id (str): RDS instance region id.
    dbinstance_id (str): RDS instance id.
    security_ips (str): security ips list, separated by commas.
    whitelist_network_type (str, optional): whitelist network type.
        - MIX: mixed network type
        - Classic: classic network
        - VPC: vpc
        default value: MIX
    security_ip_type (str, optional): security ip type.
        - normal: normal security ip
        - hidden: hidden security ip
    dbinstance_ip_array_name (str, optional): security ip array name.
    dbinstance_ip_array_attribute (str, optional): security ip array attribute.
        - hidden: hidden security ip
        - normal: normal security ip
    client_token (str, optional): idempotency token, max 64 ascii characters.

Returns:
    Dict[str, Any]: response contains request id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
region_idYes
dbinstance_idYes
security_ipsYes
whitelist_network_typeNoMIX
security_ip_typeNo
dbinstance_ip_array_nameNo
dbinstance_ip_array_attributeNo
client_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions idempotency via client_token and return type, but lacks details on destructive nature, permissions needed, or side effects.

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 structured with Args and Returns sections, but the first line is redundant with the tool name. It is not overly verbose but could be more concise.

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?

The parameter details are fairly complete, but the description lacks overall context about the operation, such as what security IPs are or the impact of modification. The return value is specified, but no output schema is provided.

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?

The schema coverage is 0%, so the description compensates well by explaining each parameter, including defaults and allowed values (e.g., whitelist_network_type options). This adds significant meaning beyond the bare schema.

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 begins with 'modify security ips', which is essentially the tool name, and does not explicitly state the broader purpose (e.g., modifying the security IP whitelist for an RDS instance). The parameter details help, but the overall purpose is vague.

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 vs alternatives, prerequisites, or exclusions. Sibling tools are listed but not referenced.

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/aliyun/alibabacloud-rds-openapi-mcp-server'

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