Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Supabase: Get auth stats

supabase_get_auth_stats
Read-only

Retrieve authentication statistics for a Supabase site, including total users, confirmed users, and provider breakdown, to monitor sign-up and login provider trends.

Instructions

[UNIFIED] Get authentication statistics including total users, confirmed users, and provider breakdown.

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

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 establishes this is a safe read, so the description's main added value is naming the returned metrics (total, confirmed, provider breakdown). It says nothing about data freshness, whether stats are per-project or global, or any auth/permission requirements needed to call it.

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 only wasted token is the unexplained '[UNIFIED]' tag, which conveys nothing actionable to an agent.

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 stats tool with no output schema, the description partially covers return content but leaves the required 'site' input entirely undefined and does not clarify the scope of the statistics. An agent knows roughly what comes back but not how to construct the one mandatory argument.

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?

The single required parameter 'site' has 0% schema description coverage, and the description does not mention it at all — no indication of what a site identifier is, what format it takes, or where to obtain it. With low coverage the description is expected to compensate, and it does not.

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 authentication statistics') and enumerates what is returned: total users, confirmed users, provider breakdown. The auth focus distinguishes it from siblings like supabase_get_database_stats and supabase_get_storage_stats, though the '[UNIFIED]' prefix is unexplained and adds no discriminating information.

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 mention of when an agent should prefer this over supabase_get_database_stats, supabase_get_storage_stats, or supabase_get_user. The only cue is the word 'auth' in the name, which the description merely restates.

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