Xpress Flow Systems

create_wallet

Create an empty Xpress wallet (no sign-up, no free credit). Returns a 32-character wallet code and an xk_live_ API key, shown once. Fund it with create_deposit on /api/mcp/wallet, then buy domains and eSIMs from the wallet balance within the caps the wallet owner sets.

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": {
      "accept_terms": "<accept_terms>"
    },
    "name": "create_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`accept_terms`	Yes	Set true only if your user agreed to the Terms of Use and Privacy Policy on this website.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent creation operation, but the description adds crucial context: the returned API key is shown only once, the wallet is empty with no free credit, and spending is constrained by wallet-owner caps. These details materially affect how an agent should handle and store the result.

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 three tightly written sentences with no filler. The most important constraint (empty wallet, no sign-up/credit) and the critical one-time secret return are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter creation tool without an output schema, the description covers the essential details an agent needs: what is created, what sensitive values are returned and shown once, and how the wallet is funded and used afterward. Nothing critical is missing.

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?

There is only one parameter, accept_terms, and its schema description is fully documented (100% coverage). The description does not add further meaning about this parameter, so a baseline score of 3 is appropriate because the schema already carries the parameter semantics.

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 uses a specific verb and resource ('Create an empty Xpress wallet') and immediately scopes it with key qualifiers ('no sign-up, no free credit'). It also states what is returned, making the operation clearly distinguishable from order-creation siblings like create_domain_order or create_esim_order.

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 explains the downstream workflow: fund the wallet with create_deposit and then use the balance to buy domains and eSIMs within owner-set caps. However, it does not explicitly state when not to create a wallet (e.g., if one already exists) or name alternatives beyond the referenced create_deposit tool.

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?