Skip to main content
Glama

auth_me

Read-onlyIdempotent

Get the current end user's profile from their authentication token.

Example:

{ "app_token": "eyJ..." }
// Returns: { "id": "u_abc", "email": "alice@example.com", "email_verified": true, "display_name": "Alice" }

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": {
      "app_token": "<app_token>"
    },
    "name": "auth_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_tokenYesApp-user JWT to validate. Returns the matching user row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's added value is the concrete example return payload (id, email, email_verified, display_name), which is useful since no output schema exists. It stops short of describing behavior for invalid or expired tokens, which is a meaningful omission for a validation tool.

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 front-loaded purpose sentence followed by a compact example; nothing is wasted, though the example partially restates what the schema already says.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool, the description plus annotations cover safety, input format, and an example of the return shape. Only error-path behavior (invalid/expired token) is left unaddressed.

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% and the single parameter already documents itself as an app-user JWT to validate. The example "eyJ..." confirms the JWT shape but adds little meaning beyond the schema.

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 the current end user's profile from an authentication token. The phrase "current end user" distinguishes it from a full user listing such as auth_users_list, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it is clearly token-validation/identity-resolving, but the description never states when to choose this over auth_login, auth_users_list, or auth_cli_pair, nor any preconditions such as the token needing to be an app-user JWT.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources