Xpress Flow Systems

verify_email_code

Step 2: check the 6-digit code your user read from their email. Returns verification_token (valid 24 hours); pass it as email_verification_token to create_domain_order, create_esim_order or create_proxy_order with the same email. 5 tries per 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_code"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	The 6-digit code.
`email`	Yes	The same email the code was sent to.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover readOnly=false and idempotent=false, and the description adds substantive behavior: the return value (verification_token), its 24-hour validity, the requirement to use the same email downstream, and a 5-try limit per code. Missing only what happens after the retry limit is exhausted or if the token is single-use.

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 front-loaded sentences with no filler: step, return contract, and usage constraint. Every sentence carries operational information an agent needs.

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?

No output schema exists, and the description compensates by naming the returned token, its lifetime, and its downstream consumers. Minor gaps around post-retry-limit behavior and token single-use keep it from being fully complete.

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 100%, so both parameters are already documented. The description restates that the code is 6-digit and that email must match the one the code was sent to, but adds no parameter meaning beyond the schema.

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 ('check') and resource ('6-digit code'), and frames it as 'Step 2', which cleanly separates it from the sibling request_email_code (step 1). An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Explicitly sets the context (after the user reads the emailed code) and names the downstream tools the returned token feeds into. No explicit 'when not to use' or failure-path guidance, but the step ordering and alternatives are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Xpress Flow Systems tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?