Skip to main content
Glama

Supabase: Query table

supabase_query_table
Read-only

Query rows from a Supabase table with PostgREST filters, sorting, column selection, and pagination. Apply operators like eq, gt, like, in, and cs to fetch exactly the records you need.

Instructions

[UNIFIED] Query data from a table with filters, sorting, and pagination. Uses PostgREST operators: eq, neq, gt, gte, lt, lte, like, ilike, in, is, cs (contains), cd (contained).

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

Input Schema

NameRequiredDescriptionDefault
siteYes
limitNo
orderNo
tableYes
offsetNo
selectNo*
filtersNo
use_service_roleNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds little behavioral context beyond that. It never explains that use_service_role bypasses row-level security, what the default limit of 100 means in practice, or whether results are truncated. For a unified query wrapper these are exactly the traits an agent needs disclosed.

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?

Two compact sentences, front-loaded with the purpose before the operator list. Every sentence carries some content, though the '[UNIFIED]' tag adds no informational value and the operator enumeration is dense with no formatting aid.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters at 0% schema coverage and no output schema, the description should explain how to build filters and what the query returns. It leaves filter syntax, pagination semantics, and service-role behavior entirely undocumented, which is insufficient for a tool of this complexity.

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 8 parameters, so the description carries the full burden — yet it only enumerates PostgREST operators for the single `filters` parameter. It does not give the filter string syntax (e.g. column.operator.value), explain `select`, `order`, `limit`/`offset` interaction, `site`, or the meaning of `use_service_role`. One of eight parameters is partially clarified.

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?

The description states a specific verb and resource — 'Query data from a table' — and adds the scoping capabilities (filters, sorting, pagination). Combined with the read-only annotation, an agent can distinguish this from write siblings like supabase_delete_rows or supabase_execute_sql. It stops short of naming alternatives explicitly, but the purpose itself is unambiguous.

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 statement of when to use this tool versus alternatives such as supabase_count_rows, supabase_execute_sql, or the table-schema tools in the sibling list. No prerequisites, no exclusions, and the '[UNIFIED]' prefix is unexplained. Usage must be inferred entirely from the verb 'Query'.

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