Skip to main content
Glama

Send the sign-up code again

resend_sign_up_code

Sends a new code for a pending registration (at most once a minute; the answer is the same whether or not one is pending). [REST: POST /api/auth/register/resend]

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": "resend_sign_up_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

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

B3.4/5.0
Behavior4/5

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

Annotations only give the generic safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds two genuinely non-obvious traits: a one-per-minute rate limit and a uniform response regardless of whether a registration is pending. Together these tell an agent how to reason about retries and about the response being uninformative, though it does not say what happens on throttling.

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?

A single front-loaded sentence with the rate limit and response-consistency caveat attached immediately, plus the REST endpoint as a trailing tag. Nothing is redundant, though the REST hint is low-value for an agent that already has the tool name.

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

Completeness3/5

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

For a two-parameter, no-output-schema tool with annotations present, the description covers purpose and the two most surprising behaviors. It still leaves the required email parameter unexplained and says nothing about the failure/throttle outcome, which is the main thing an agent needs before retrying.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: lang carries a full enum description, but email is required with only length bounds and no explanation, and the description says nothing about either parameter. It therefore does not compensate for the undocumented half, leaving the agent to guess whether email must match the pending registration.

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: sends a new verification code for a *pending* registration, which implicitly separates it from sign_up (start a registration) and confirm_sign_up (submit a code). It never names those siblings, so the differentiation must be inferred from the word 'pending'.

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?

The parenthetical makes the preconditions clear enough (a registration is pending, and at most one request per minute), which implies when the tool is appropriate. However there is no explicit 'use this instead of X' routing and no statement of what to do when the rate limit is hit.

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