Skip to main content
Glama

auth_login

Sign in user, authenticate, login user, password check, end-user login — log in an existing end user of your app. Returns user profile, authentication token, and session token.

Example:

{ "project_id": "my-saas", "email": "alice@example.com", "password": "s3cure!Pass" }
// Returns: { "user": { "id": "u_abc", "email": "alice@example.com" }, "token": "eyJ...", "session_token": "st_...", "refresh_token": "rt_..." }

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": {
      "project_id": "<project_id>",
      "email": "<email>",
      "password": "<password>"
    },
    "name": "auth_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesUser's email
passwordYesUser's password
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

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 declare a non-read-only, non-idempotent, non-destructive operation, and the description goes beyond that by disclosing the return payload: user profile, authentication token, session token, and (in the example) a refresh token. Since there is no output schema, this is genuinely useful added context. It still omits failure modes, rate limiting, and token lifetimes, which keeps it from a 5.

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?

The purpose and return values are front-loaded and the example is compact and illustrative. However, the leading synonym list ('Sign in user, authenticate, login user, password check, end-user login') is redundant keyword padding that duplicates the sentence immediately following it.

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 three-required-parameter authentication tool with no output schema, the description covers what it does, what it returns, and a full request/response example. The main gaps are error behavior (bad password, ambiguous project) and how the returned tokens should be used, which an agent would benefit from knowing.

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 100%, so all three parameters are already fully documented, including the nuanced project_id resolution rules. The description only echoes those fields through an example with sample values ('my-saas', an email, a password), adding little meaning beyond the schema. Baseline 3 applies.

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?

The description states a concrete verb and resource: 'log in an existing end user of your app', and it explicitly scopes to existing users, which implicitly separates it from auth_signup. The opening synonym pile ('Sign in user, authenticate, login user, password check') muddies rather than sharpens the purpose, and no sibling is named outright, 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 Guidelines3/5

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

Usage is only implied: 'an existing end user' signals this is for users who already have accounts, and the worked example shows a typical call. There is no explicit when-not guidance, no mention of what to do when credentials fail, and no named alternative such as auth_signup for new users.

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