Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get function info

supabase_get_function_info
Read-only

Retrieve configuration and details for a specific Supabase Edge Function to inspect how it is set up.

Instructions

[UNIFIED] Get information about a specific Edge Function including its configuration.

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>",
      "function_name": "<function_name>"
    },
    "name": "supabase_get_function_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
function_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description carries only residual burden. 'Including its configuration' is the sole added detail — it does not say whether sensitive values (env vars, secrets) are exposed, whether the call fails for undeployed functions, or what the shape of the returned config is. Barely more than a restatement of the title.

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 no filler. The '[UNIFIED]' tag is noise, but the rest is efficient and readable.

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?

The tool is simple (2 params, no output schema, read-only), so a short description is defensible. However, with undocumented parameters and no statement of the returned configuration fields, an agent must guess at both input formats and output contents.

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% for two required parameters. The description does not clarify what 'site' means (project ref, URL, or instance name) or the format expected for 'function_name' (slug vs ID). With zero schema documentation, the description had full responsibility here and supplies nothing.

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 ('Get information') and a specific resource ('a specific Edge Function'), plus a hint of scope ('including its configuration'). An agent can distinguish it from invoke/get_url siblings by the word 'configuration', though the description never explicitly contrasts them.

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 the many siblings (supabase_get_function_url, supabase_check_function_health, supabase_invoke_function_get). No prerequisites, no mention of when the function must already exist or be deployed.

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