Skip to main content
Glama

Confirm e-mail

confirm_email

Confirm the e-mail address with the 6-digit code from the confirmation mail (or confirm the phone with the code from send_verification_sms). Without a code, the confirmation mail (link + new code) is sent again. Codes are valid 10 minutes, the link 24 hours.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "confirm_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe 6 digits the learner read out. Omit to resend the mail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds real behavioral context beyond that: codes expire in 10 minutes, the link in 24 hours, and a call without a code is not a confirmation but a resend. It stops short of saying what happens on an invalid or expired code, or whether a resend invalidates an earlier code, which keeps it from a 5.

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?

Three short sentences, front-loaded with the primary action, then the fallback, then the validity constraints. Nothing is repeated from the schema verbatim and no sentence is 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 single-parameter mutation tool with no output schema and modest annotation coverage, the description supplies the essential context: both verification channels, the resend fallback, and expiry windows. It is slightly incomplete regarding failure modes and what the response looks like on success versus failure, but the tool is simple enough that this is a minor gap.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents the omit-to-resend behavior, so the baseline is 3. The description still adds meaning the schema does not: the code may come from an SMS verification flow as well as the confirmation mail, and it must be the 6-digit value with a 10-minute validity window.

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 ('Confirm the e-mail address') and immediately covers the second supported target ('or confirm the phone'), so the agent knows this one tool handles both verification channels. It also names the sibling send_verification_sms as the code source for the phone path, which distinguishes it from the other tools in the family.

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?

The description gives an explicit branching rule: pass the 6-digit code to confirm, omit the code to have the confirmation mail (link + new code) re-sent. It also implies the prerequisite flow for phone confirmation, which is to obtain the code via send_verification_sms first. That is enough for an agent to pick the correct call without inference.

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