Skip to main content
Glama
Sign In
Alibaba Cloud RDS OpenAPI MCP Server

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

attach_whitelist_template_to_instance

Attach a whitelist template to an RDS instance to control IP access. Specify the region, instance, and template ID.

Instructions

allocate db instance public connection.
Args:
    region_id: The region ID of the RDS instance.
    db_instance_id: The ID of the RDS instance.
    template_id: Whitelist Template ID. Can be obtained via DescribeAllWhitelistTemplate.
Returns:
    dict[str, Any]: The response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region_id": "<region_id>",
      "db_instance_id": "<db_instance_id>",
      "template_id": "<template_id>"
    },
    "name": "attach_whitelist_template_to_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
region_idYes
template_idYes
db_instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations provided. The description does not disclose behavioral traits (e.g., permissions, side effects, idempotency). The mismatch between description and name creates confusion, not transparency.

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

Conciseness2/5

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

The description is short but the main sentence is inaccurate and misleading. Conciseness is undermined by incorrect content.

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?

No output schema, no error handling information, no examples. The parameter explanations are minimal. The core action is misrepresented, making the tool contextually incomplete.

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?

Despite 0% schema description coverage, the description provides brief explanations for all three parameters (e.g., 'region_id: The region ID of the RDS instance'), adding meaning beyond the schema's property names and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'allocate db instance public connection' which contradicts the tool name 'attach_whitelist_template_to_instance'. This is misleading and does not clarify the actual purpose.

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 vs siblings like 'allocate_instance_public_connection' or 'describe_all_whitelist_template'. Agent has no context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools