Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

describe_error_logs

Read-only

Retrieve error logs from an Alibaba Cloud RDS instance to diagnose database issues by specifying a time range.

Instructions

Query error logs of an RDS instance.
Args:
    region_id: The region ID of the RDS instance.
    db_instance_id: The ID of the RDS instance.
    start_time: The start time of the query. Format: yyyy-MM-dd HH:mm.
    end_time: The end time of the query. Format: yyyy-MM-dd HH:mm.
    page_size: The number of records per page. Range: 30~100. Default: 30.
    page_number: The page number. Default: 1.
Returns:
    Dict[str, Any]: A dictionary containing error log information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_timeYes
page_sizeNo
region_idYes
start_timeYes
page_numberNo
db_instance_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the tool is known to be safe. The description adds parameter format details but doesn't disclose additional behavioral traits beyond the schema.

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 structured with 'Args:' and 'Returns:' sections, clearly listing parameters. It is efficient without fluff, though not extremely 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 presence of an output schema, the return type note is sufficient. The description covers required parameters, pagination, and time format, making it complete for the tool's complexity.

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 description coverage, the description carries full burden. It explains all 6 parameters, including format for start_time and end_time, and range for page_size, which adds value beyond the schema.

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 'Query error logs of an RDS instance,' specifying the verb and resource. It distinguishes itself from sibling tools like describe_slow_log_records and describe_db_instance_performance.

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 alternatives like describe_slow_log_records. The description lacks context on typical use cases or exclusions.

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