Skip to main content
Glama

Signup

signup

Create an account for a person's email and a Manage key for this agent; the person claims the account from the claim link. 5 per IP and 300 in all a day. Creates an account for the person's email, with a seven-day Solo trial and a Manage key for this agent, and emails them a claim link. The trial is once per person: a mailbox that had one (plus tags and Gmail dots count as the same mailbox), or a second sign-up from one network within 30 days, gets the account on Free with no trial, and the response says so in fix. 409 email_taken when the address already has an account: its owner makes a key under Account → API keys instead. Limited to 5 sign-ups per IP and 300 in all a day (429 rate_limited).

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": {
      "email": "<email>"
    },
    "name": "signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's address. The account is theirs; the claim email goes there.
useCaseNoWhat the person wants a dashboard for, in a sentence.
agentNameNoThe agent or product making the account, such as Claude Code. Names the key and is mentioned in the claim email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it discloses the seven-day Solo trial, once-per-person eligibility including mailbox tags and Gmail dots, the 30-day network restriction, the claim email, the Manage key, and the 409 and 429 error behaviors. This is rich behavioral context for a mutating operation.

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 core purpose is front-loaded, but the description repeats the account-creation and rate-limit information in multiple sentences. It is informative yet unnecessarily redundant.

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 mutation tool with no output schema, it covers account creation, trial rules, the claim link, key creation, and key error outcomes. Minor gaps remain around exactly what the response body contains and any other failure modes.

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 input schema already defines email, useCase, and agentName. The description ties the key and claim email to the agent and person, but does not add parameter syntax or constraints beyond the schema.

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 states a specific verb and resource: create an account for the person's email plus a Manage key for the agent, with a claim link. This is unambiguous and not a restatement of the name.

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?

It explains the intended action, describes rate limits, and gives a clear alternative for the 409 email_taken case. It lacks an explicit general when-not-to-use statement or alternative signup path beyond the already-registered-email case.

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