Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get table indexes

supabase_get_table_indexes
Read-only

Retrieve a table’s primary keys, unique constraints, and custom indexes to inspect its schema and support Supabase database management.

Instructions

[UNIFIED] Get indexes for a table including primary keys, unique constraints, and custom indexes.

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>",
      "table": "<table>"
    },
    "name": "supabase_get_table_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
tableYes
schemaNopublic

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lower. It adds useful substance by specifying the content returned (primary keys, unique constraints, custom indexes), but says nothing about permissions, whether indexes from other schemas are included, or result shape.

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 the resource stated first and the returned content appended. The "[UNIFIED]" prefix is noise that adds no meaning, but otherwise there is no wasted wording.

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 simple read-only lookup with no output schema, the description covers what is returned, which is the main thing an agent needs. However, with three undocumented parameters and a near-identical sibling (get_table_constraints), the definition is not complete enough to guarantee a correct, unambiguous invocation.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not: only "for a table" loosely implies the table argument. Nothing explains what site refers to or that schema defaults to public, which are the non-obvious parts of the call.

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 ("Get indexes for a table") and enumerates the index categories returned (primary keys, unique constraints, custom indexes), which meaningfully separates it from a generic schema fetch. It does not explicitly name or contrast with the close sibling supabase_get_table_constraints, so differentiation still requires the agent to infer the boundary.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent deciding between this and supabase_get_table_constraints or supabase_get_table_schema gets no routing signal from the description.

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