Alibaba Cloud RDS OpenAPI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

describe_db_instance_net_info

Read-only

Batch retrieves network configuration details for multiple Alibaba Cloud RDS instances by providing region ID and instance IDs.

Instructions

Batch retrieves network configuration details for multiple RDS instances.
Args:
    region_id: The region ID of the RDS instance.
    db_instance_ids: List of DB instance identifiers (e.g., ["rm-uf6wjk5****", "db-instance-01"])
Returns:
    list[dict]: A list of dictionaries containing network configuration details for each instance.

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_ids": "<db_instance_ids>"
    },
    "name": "describe_db_instance_net_info"
  }
}

Input Schema

Name	Required	Description	Default
`region_id`	Yes
`db_instance_ids`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

A3.8/5.0

Behavior3/5

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

The description is consistent with the readOnlyHint annotation (read-only retrieval). It adds the batch behavior but no further behavioral details beyond what annotations already convey. It does not contradict annotations.

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 extremely concise, with a single-purpose sentence followed by structured Args and Returns sections. Every word adds value, and the most important action is front-loaded.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema, the description provides sufficient information about inputs and outputs. It lacks edge cases or prerequisites but is functionally complete for typical use.

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?

With 0% schema coverage, the description compensates by explaining the purpose of each parameter and providing an example for db_instance_ids. This adds meaningful context beyond the schema types.

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 verb 'retrieves' and the resource 'network configuration details for multiple RDS instances', which is specific and distinguishes it from sibling tools that describe other aspects like attributes or databases.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It only states the tool's function.

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

Deploy Server