Skip to main content
Glama

auth_signup

Register user, create account, new user, sign up, onboard user — sign up a new end user for your app. Returns registration and user metadata; credentials are omitted from MCP output. This result cannot sign an agent in from a transcript. Sign-in goes through the app’s normal secure sign-in flow. Passwords are securely hashed. Intended for server-side code, not browser code.

Example:

{ "project_id": "my-saas", "email": "alice@example.com", "password": "s3cure!Pass" }
// Returns registration and user metadata without authentication credentials.

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

Input Schema

NameRequiredDescriptionDefault
nameNoAlias for display_name
emailYesUser's email
fullNameNoAlias for display_name
passwordYesMin 8 characters. Securely hashed server-side.
full_nameNoAlias for display_name
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).
displayNameNoAlias for display_name
display_nameNoOptional display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, so the description's added value is in disclosing that credentials are omitted from output, passwords are hashed server-side, and the result cannot authenticate a transcript. The notable gap is duplicate-email behavior, which matters given idempotentHint=false but is never addressed.

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

Conciseness3/5

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

The body is tight and front-loads the security-relevant facts, but the opening synonym list is pure keyword padding that occupies the most prominent position. The example block earns its place by showing a concrete project_id form.

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 an 8-parameter mutation with no output schema, the description covers return shape (registration and user metadata, no credentials), security posture, and execution environment. Failure modes such as a taken email or an ambiguous multi-project account are left to the schema's error note and not addressed here.

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 the alias fields and the project_id resolution rules are already fully documented upstream. The description's example reinforces that project_id accepts a slug like 'my-saas' rather than a UUID, but adds no new parameter meaning beyond what the schema states.

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 core sentence states a specific verb and resource: sign up a new end user for the app, and the annotations corroborate with 'Create an end-user account.' It separates itself from sign-in by stating that this result cannot sign an agent in, though the leading keyword-stuff chain ('Register user, create account, new user, sign up, onboard user') muddies rather than sharpens the purpose.

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

Usage Guidelines4/5

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

Gives clear operating context: intended for server-side code, not browser code, and explicitly not a sign-in path. What's missing is an explicit pointer to the sign-in sibling (auth_login) or a statement about what to do when the email already exists.

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