Aliyun RDS Supabase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

install_execute_sql_function

Installs the execute_sql function in your Supabase instance, enabling SQL query execution for tools like list_tables and execute_sql without direct database access.

Instructions

Install the execute_sql RPC function in the connected Supabase instance. This function is required for tools that need to execute SQL queries (list_tables, list_extensions, execute_sql, etc.). This tool uses the postgres-meta API and does not require direct database access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "install_execute_sql_function"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jul 14, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions that the tool uses the postgres-meta API and does not require direct database access, but does not disclose whether the operation is idempotent, what happens if the function already exists, or any required permissions. This lack of detail is notable for a mutation tool.

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 two sentences long, front-loaded with the action, and contains no redundant information. Every sentence adds value by explaining the purpose and prerequisite nature.

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 (zero parameters, no output schema), the description adequately covers purpose, usage context, and technical approach (postgres-meta API). It lacks information on success/failure indicators or idempotency, but these are minor omissions for a setup tool.

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?

The tool has no parameters, so the baseline is 4. The description adds context about using the postgres-meta API and not needing direct DB access, which is informative but not parameter-related. Since schema coverage is 100%, no further parameter documentation is needed.

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 installs an execute_sql RPC function and explains it's required for tools that execute SQL queries. It specifies the verb 'install' and the resource 'execute_sql RPC function', distinguishing it from sibling tools which do not perform this setup.

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

Usage Guidelines4/5

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

The description implies when to use the tool: before using tools that need SQL execution capability (list_tables, etc.). It does not explicitly state when not to use it or alternatives, but the context is sufficiently clear for a setup tool.

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