Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get user

supabase_get_user
Read-only

Retrieve detailed profile information for a specific Supabase user by ID and site, so you can inspect account data directly.

Instructions

[UNIFIED] Get detailed information about a specific user by their ID.

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>",
      "user_id": "<user_id>"
    },
    "name": "supabase_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing beyond that: no statement of what happens when the user does not exist, whether admin/service-role credentials are required, or whether the lookup is scoped to the site in the `site` parameter. For a multi-tenant admin tool this is a real gap.

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 resource and lookup key come first. The only waste is the unexplained "[UNIFIED]" tag, which consumes attention without conveying actionable meaning.

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?

It is a simple two-parameter read tool with no output schema, so return-value explanation is not required and annotations cover the safety profile. What remains missing is the meaning of `site` and any hint about required permissions or not-found behavior, which matters for correct invocation.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does clarify that `user_id` is an identifier lookup, but provides no format detail (UUID vs numeric) and leaves the `site` parameter entirely unaddressed in both schema and description. Half the parameter surface is undocumented.

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 information about a specific user") and narrows the lookup key to an ID, which distinguishes it in spirit from supabase_get_user_by_email. The "[UNIFIED]" prefix is unexplained jargon and the description never explicitly names the sibling it contrasts with, so it stops short of a 5.

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 supabase_get_user_by_email, list-style siblings, or admin endpoints. An agent must infer the selection rule purely from the tool name, which the scoring rubric says should not be the basis for guidance.

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