Skip to main content
Glama

Confirm the account and get an API key

confirm_sign_up

Confirms the registration with the emailed code and the signup_token of sign_up, and returns an API key for this MCP server (shown once). [REST: POST /api/auth/register/verify]

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>",
      "code": "<code>",
      "signup_token": "<signup_token>"
    },
    "name": "confirm_sign_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
langNoThe account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
emailYes
key_daysNoLifetime of the key in days; null = no limit. Default 365.
key_nameNoName of the API key in Settings (default «MCP agent»).
key_accessNofull
signup_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"The account's language (messages, the texts of its searches). Default en."New value: +"The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "ru",
      -  "en"
      -]New value: +[
      +  "ru",
      +  "en",
      +  "es",
      +  "de",
      +  "fr",
      +  "pt",
      +  "ja"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds a genuinely important trait beyond the annotations: the API key is "shown once," so the agent knows to surface it immediately. Annotations already declare non-readonly, non-destructive, non-idempotent. Missing is what happens when the code is expired or already used.

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

Conciseness5/5

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

Two tightly packed sentences with the outcome and the one-time-reveal warning front-loaded, plus a compact REST route annotation. No filler.

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 7-parameter mutation with no output schema, the description covers the essential result (an API key, shown once) and the prerequisite flow. The key-minting parameters are underspecified, but the core call path is clear.

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 43%, and the description explains only the two inputs it names (emailed code, signup_token). It says nothing about email, lang, key_days, key_name or key_access, so the key-minting knobs (lifetime, access level, key name) are left entirely to the schema, with key_access carrying an enum but no description anywhere.

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?

States a specific verb and resource ("Confirms the registration") plus its outcome ("returns an API key"), and anchors itself relative to the sign_up sibling whose signup_token it consumes. An agent can tell this is the second step of registration, not a re-send or a sign-in.

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 implied rather than stated: the mention of "the signup_token of sign_up" makes the ordering clear, but there is no explicit when-to-use, no mention of the resend_sign_up_code sibling for expired codes, and no failure/retry guidance.

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