Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Enable extension

supabase_enable_extension
Destructive

Enable PostgreSQL extensions such as pgvector, PostGIS, or uuid-ossp on a Supabase site, specifying the target schema so database features are available for your project.

Instructions

[UNIFIED] Enable a PostgreSQL extension (e.g., pgvector, postgis, uuid-ossp).

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": {
      "site": "<site>",
      "name": "<name>"
    },
    "name": "supabase_enable_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes
schemaNoextensions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the description adds no safety context of its own. It does not say whether enabling is reversible, that supabase_disable_extension undoes it, or what happens if the extension is already installed or unsupported on the instance.

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?

A single front-loaded sentence with zero wasted words and a useful example list. It is efficiently structured, though its brevity reflects under-specification rather than tight editing.

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?

For a destructive mutation with no output schema and 0% parameter coverage, an agent still lacks permission requirements, failure behavior, and the meaning of `site` and `schema`. The annotations cover the risk profile, but the description leaves real operational gaps for a mutating tool.

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 description coverage is 0% with three parameters, so the description must compensate, and it only partially does: examples clarify the `name` parameter, but `site` and `schema` (default 'extensions') are not explained at all. The examples are helpful but leave two of three parameters semantically undefined.

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?

States a specific verb and resource: 'Enable a PostgreSQL extension', backed by concrete examples (pgvector, postgis, uuid-ossp). The inverse sibling supabase_disable_extension is obvious from the naming, though the description never names or contrasts it explicitly.

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 versus alternatives such as supabase_execute_sql (which could also issue CREATE EXTENSION), and no prerequisites mentioned, such as required role or that the extension must not already be installed. Usage is only implied by the tool name.

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