Skip to main content
Glama

register_mentee

Legacy in-chat email signup for MCP clients that do NOT manage OAuth Connect (no Claude Code, Cursor, or ChatGPT Connect). If the client sends Authorization or apply returns use_connect/token_expired, use Connect (/mcp) instead — never call this on Connect clients.

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

Input Schema

NameRequiredDescriptionDefault
emailYes
last_nameNo
first_nameNo

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

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the description's job is to add context beyond that, which it does by disclosing the legacy status and the failure signals (use_connect, token_expired) that mean the call should never have been made. It stops short of describing write semantics such as duplicate-email handling, idempotency, or whether an account is created immediately.

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 tight sentences, with the scope-defining 'legacy / not for OAuth clients' constraint front-loaded before the fallback instruction. No filler or restatement of 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?

The routing guidance is thorough and an output schema exists so return values need no explanation, but for a three-parameter mutation the description leaves parameter meaning and write-side effects (duplicates, verification, idempotency) unaddressed. Adequate to prevent misrouting, incomplete as a full behavioral contract.

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 description coverage is 0% across three parameters, so the description carries the full burden of explaining them and says nothing about email, first_name, or last_name. It never clarifies that email is the required identifier or that the name fields are optional and default to empty strings.

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 description names a specific action and resource: 'Legacy in-chat email signup' for registering a mentee, and it explicitly marks this as the non-OAuth path. An agent can tell what it does without reading the schema, though it never states plainly that it creates a mentee record or how that differs from sibling tools like apply_to_mentor.

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 concrete when-not conditions: do NOT use on clients that manage OAuth Connect (Claude Code, Cursor, ChatGPT Connect), and do not use if an Authorization header is present or a call returns use_connect/token_expired. It names the replacement path (/mcp Connect) for those cases, so the routing decision is fully specified.

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