Skip to main content
Glama
Sign In
Aliyun RDS Supabase MCP Server

Aliyun RDS Supabase MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apply_migration

Apply a SQL migration script and record it in the supabase_migrations.schema_migrations table within a transaction, ensuring atomic schema updates on Aliyun RDS Supabase.

Instructions

Applies a SQL migration script and records it in the supabase_migrations.schema_migrations table within a transaction. Requires direct database connection (DATABASE_URL).

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": {
      "version": "<version>",
      "sql": "<sql>"
    },
    "name": "apply_migration"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesThe SQL DDL content of the migration.
nameNoAn optional descriptive name for the migration.
versionYesThe migration version string (e.g., '20240101120000').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses key behaviors: runs in a transaction, records in supabase_migrations.schema_migrations, and requires DATABASE_URL. However, it lacks details on failure modes, idempotency, or side effects.

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?

Two sentences, front-loaded with the core action and key context (transaction, recording, database connection). No wasted words.

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 complexity (modifies database, 3 params, no output schema), the description covers main aspects but omits return behavior and potential error conditions. Adequate but not fully complete.

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?

Schema coverage is 100%, so baseline is 3. The description does not add extra meaning beyond what the schema already provides for parameters (version, sql, name).

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 tool applies a SQL migration script and records it in a specific table within a transaction. It distinguishes itself from execute_sql by mentioning the recording step and transaction context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for applying migrations but does not explicitly state when to use this tool over alternatives like execute_sql or list_migrations. No exclusions or prerequisites beyond database connection are mentioned.

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