Xpress Flow Systems

request_email_code

Step 1 before any create_*_order: email a 6-digit code to the buyer. Ask your user for the code from that email (it expires in 10 minutes; a new one can be sent after 60 seconds, at most 5 an hour).

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

Input Schema

Name	Required	Description	Default
`email`	Yes	The buyer's email address.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it sends a 6-digit code by email, the code expires in 10 minutes, resend is possible after 60 seconds, and there is a rate limit of 5 per hour. These are exactly the operational details an agent needs and are not present in the annotations.

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?

The description is front-loaded with the critical dependency ('Step 1 before any create_*_order') and packs the expiry, cooldown, and rate limit into a compact parenthetical. Every sentence earns its place with no wasted text.

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 one-parameter tool with rich annotations and no output schema, this covers the key prerequisites and rate-limit behavior. The main remaining gap is that it does not explicitly describe the return behavior or name the follow-up verification tool, leaving a small amount of flow context implicit.

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% and the single parameter is already documented as the buyer's email address. The description reiterates that the code goes to the buyer, but adds no syntax, formatting, or validation detail 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?

The description states a specific action and resource: emailing a 6-digit confirmation code to the buyer's email. It also distinguishes this tool from the create_*_order siblings by positioning it as a prerequisite step, so an agent can tell exactly what this tool does and where it sits in the flow.

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?

It clearly says to use this as 'Step 1 before any create_*_order' and instructs the agent to ask the user for the emailed code. That is strong contextual guidance, though it does not explicitly name verify_email_code as the next tool or state exclusions beyond the order-creation flow.

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?