Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get table schema

supabase_get_table_schema
Read-only

Retrieve detailed schema information for a Supabase table, including columns, data types, constraints, and defaults, to understand or validate database structure.

Instructions

[UNIFIED] Get detailed schema information for a table including all columns, data types, constraints, and defaults.

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_schema"
  }
}

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.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description helpfully discloses what the payload contains (columns, data types, constraints, defaults). It says nothing about permissions, behavior when the table does not exist, or cost/latency, which is acceptable given annotation coverage but leaves gaps.

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 key content first and no filler beyond the unexplained "[UNIFIED]" tag. It is appropriately sized for a simple read tool.

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?

There is no output schema, and the description does partially compensate by naming the returned fields. However, with zero parameter documentation and no differentiation from the constraints/indexes siblings, an agent cannot reliably map arguments or choose this tool confidently.

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 is the only source of meaning and it supplies almost none. It never explains the required `site` or `table` parameters, and it leaves the `schema` parameter ambiguous between a database schema and the table's structure, even though it defaults to "public".

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 detailed schema information for a table" with the returned fields enumerated. It does not distinguish itself from close siblings like supabase_get_table_constraints or supabase_get_table_indexes, so an agent cannot tell from the text alone which of the three to call for constraint data.

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?

Usage is only implied by the verb "Get" and the object "table schema"; there is no explicit when-to-use statement and no exclusions or alternatives named. The unexplained "[UNIFIED]" prefix adds no routing information an agent can act on.

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