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

show_largest_table_fragment

Read-only

Queries the tables with the largest fragments in an RDS instance, enabling targeted optimization of database storage.

Instructions

Query the tables with the largest table fragments

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>",
      "dbinstance_id": "<dbinstance_id>"
    },
    "name": "show_largest_table_fragment"
  }
}

Input Schema

NameRequiredDescriptionDefault
topKNoTo display the number of the top few largest tables
region_idYesThe region ID of the RDS instance.
dbinstance_idYesThe ID of the RDS instance.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description uses 'Query' which aligns. No additional behavioral traits are disclosed (e.g., performance, permissions). With annotations present, the bar is lower, so a score of 3 is appropriate.

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 a single, concise sentence (7 words) that is front-loaded with the action. It earns its place but could benefit from a bit more detail on scope.

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?

Given the tool's moderate complexity (3 params, output schema exists), the description is minimal. It doesn't elaborate on return values or ordering, but the output schema presumably covers that. Not complete enough for higher score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100% with descriptions for all parameters. The description adds no extra meaning beyond the schema (e.g., it doesn't explain how topK relates to fragment size). Baseline 3 is adequate.

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

Purpose4/5

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

The description 'Query the tables with the largest table fragments' clearly states the action (query) and the target (tables with largest fragments). It is specific, though it does not explicitly differentiate from sibling 'show_largest_table' which may cover overall table sizes.

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 versus alternatives like 'show_largest_table' or others. No prerequisites or usage context are given.

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