Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get instance info

supabase_get_instance_info
Read-only

Retrieve a Supabase instance's base URL and available API endpoints to connect tools and configure integrations.

Instructions

[UNIFIED] Get Supabase instance information including base URL and available API endpoints.

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": "supabase_get_instance_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

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 bar is lower. The description does add value by naming the returned payload (base URL plus available API endpoints), which matters because there is no output schema, but it omits auth requirements and any caveats about what is exposed.

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?

One sentence, front-loaded with the verb and resource, with no filler. The '[UNIFIED]' prefix adds slight noise without semantic content, but nothing else is wasted.

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 the description is close to sufficient, and it compensates somewhat for the missing output schema by naming the returned fields. It falls short on the sole required parameter and on any environment or permission context.

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?

There is a single required parameter, 'site', with 0% schema description coverage, and the description never mentions it. The agent gets no hint about whether 'site' is a project ref, a subdomain, or a full hostname, which is the one piece of information needed to invoke the tool correctly.

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 uses a specific verb ('Get') and resource ('Supabase instance information') and enumerates what is returned (base URL, available API endpoints). It does not, however, distinguish itself from similar siblings such as supabase_get_public_url or supabase_get_service_status, so an agent must guess which 'info' tool to pick.

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 guidance, no prerequisites, and no named alternative among the many sibling get_*_info tools. The '[UNIFIED]' tag hints at a cross-provider convention but does not tell the agent when this tool is the right choice over supabase_get_public_url or supabase_get_service_status.

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