Skip to main content
Glama

verify_email

Legacy in-chat email confirmation for non-Connect MCP clients only. Returns a Bearer JWT only if the client will send it on later requests (most Connect clients will not). If Authorization is already sent, returns use_connect — run /mcp instead. Never invent the code.

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>"
    },
    "name": "verify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
emailYes

Output Schema

NameRequiredDescriptionDefault
emailNoNormalized email.
errorNoError code: invalid_email, invalid_code, human_required, rate_limit_exceeded, etc.
accessNoJWT access token. Send as Authorization: Bearer.
statusNo'code_sent' after register, 'verified' after verify.
messageNoHuman-readable error or status detail.
refreshNoJWT refresh token.
mentee_idNoMentee id after verify.
next_stepNoWhat to do next.
expires_inNoAccess token lifetime in seconds. Currently 12 hours.
token_typeNoAlways 'Bearer' when tokens are present.
verify_urlNoBrowser page where the human completes Cloudflare Turnstile.
mail_verifiedNoTrue after a successful verify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, openWorldHint true), the description discloses that a Bearer JWT is issued only conditionally and that a use_connect sentinel may be returned instead of a token. The "Never invent the code" warning flags a required authoritative input, which annotations cannot express. What remains unstated is failure behavior for an invalid or expired code.

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?

Four short sentences, front-loaded with the legacy/non-Connect scoping that determines whether the agent should call it at all. The telegraphic phrasing ("run /mcp instead") is dense but unambiguous; nothing is padded.

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?

With an output schema present, return values need no explanation, and the description still flags the two response shapes (JWT vs use_connect) that matter for decision-making. For a two-parameter tool with annotations and an output schema, the remaining gap — error behavior and where the code originates — is minor.

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 0%, so the description must carry parameter meaning. It adds a real constraint for `code` (never fabricate it, take it from the user/message), but says nothing about `email` — format, whether it must match the account on file, or case handling. Partial compensation only.

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?

"Legacy in-chat email confirmation" names a specific verb (confirm) and resource (email), and the scope qualifier "for non-Connect MCP clients only" narrows it sharply. It is not differentiated against any sibling tool, but no sibling in the list performs email verification, so the ambiguity is minimal.

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

Usage Guidelines5/5

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

It gives explicit when-to-use (non-Connect clients that will reuse the Bearer JWT), explicit when-not ("If Authorization is already sent ... run /mcp instead"), and names the alternative endpoint plus the exact sentinel response (use_connect) that signals the wrong path was taken.

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