Retrieve detailed attributes of an RDS instance by specifying its region and ID.
Queries the details of an instance.
Args:
region_id: db instance region(e.g. cn-hangzhou)
db_instance_id: db instance id(e.g. rm-xxx)
:return:| Name | Required | Description | Default |
|---|---|---|---|
| region_id | Yes | ||
| db_instance_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true. The description only repeats 'Queries' without adding behavioral context like rate limits, authentication needs, or result behavior. No added value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but includes unnecessary 'Args:' and ':return:' lines without providing a return description. The core information is minimal but could be more efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, yet the description fails to describe return values or structure. The agent has no clue what 'details' are returned. Also missing error handling or edge case information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, but the description adds examples for both parameters (e.g., 'cn-hangzhou' for region_id, 'rm-xxx' for db_instance_id), which clarifies expected values. This compensates for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Queries the details of an instance' with specific verb and resource. It lists required arguments with examples. However, it does not distinguish itself from sibling describe tools like 'describe_db_instance_accounts' or 'describe_db_instance_databases', leaving room for ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus others, such as 'describe_db_instances' for listing instances. No prerequisites or usage conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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