Skip to main content
Glama
Sign In
Aliyun RDS Supabase MCP Server

Aliyun RDS Supabase MCP Server

Official
by aliyun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_auth_user

Retrieves user details from auth.users using their UUID.

Instructions

Retrieves details for a specific user from auth.users 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": {
      "user_id": "<user_id>"
    },
    "name": "get_auth_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe UUID of the user to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'retrieves', which is a read operation, but does not disclose potential side effects, error cases, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no unnecessary words. It is front-loaded and efficient.

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 single-parameter read tool without output schema, the description is minimally adequate. It could benefit from mentioning what 'details' are returned or handling of non-existent users.

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 coverage is 100%, so the description adds little beyond 'by their ID'. The parameter is already fully described in the schema. No additional semantic value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retrieves', the resource 'details for a specific user', and the method 'by their ID'. It distinctly separates from siblings like list_auth_users or create_auth_user.

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 tool versus alternatives like list_auth_users or other user-related tools. The description does not mention context, prerequisites, or exclusions.

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