Xpress Flow Systems

create_cart_order

Start one purchase for several eSIMs and proxy packs together: one payment_url for the whole total, in US dollars outside Nigeria and in naira in Nigeria. This does not charge anyone. After a verified payment, details for each item arrive by email and on its order page. Returns each item reference with its own status_url. Poll get_cart_status with reference and status_token.

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": {
      "items": "<items>",
      "email": "<email>",
      "accept_terms": "<accept_terms>"
    },
    "name": "create_cart_order"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Required: the person's email, for receipts and order details.
`items`	Yes	Items: { kind: "esim", location, plan_code, qty } or { kind: "proxy", product, gb, offer_id, target_country, qty }. qty 1 to 5.
`country`	No	Optional: the payer's two-letter country. Outside Nigeria (NG) they pay in US dollars.
`currency`	No	Optional: USD or NGN. By default prices are in US dollars outside Nigeria and in naira inside Nigeria, from where the request comes from.
`accept_terms`	Yes	Set true only if your user agreed to the Terms of Use and Privacy Policy on this website.
`email_verification_token`	No	verification_token from verify_email_code for this email (required while email checks are on).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the bar is lower, yet the description still adds real value: it clarifies that no charge occurs at creation despite the word "purchase", and describes the post-payment delivery path. It does not mention that repeated calls create separate carts (non-idempotent) or any failure/limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with capability, then cost behavior, then return shape, then next step. Nothing is padding, though the currency sentence duplicates a rule the schema already encodes and could be trimmed.

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?

With no output schema, the description carries the return contract and does so adequately: payment_url, per-item reference and status_url. It also covers the no-charge semantics and email delivery. Gaps are minor: no mention of the 10-item cap, per-line qty limits, or what happens on payment failure.

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 description coverage is 100%, so the baseline is 3. The description's currency detail ("US dollars outside Nigeria and in naira in Nigeria") largely restates what the currency and country schema entries already say; its only true addition is tying the returned reference and status_token to the get_cart_status polling call.

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?

"Start one purchase for several eSIMs and proxy packs together" names a concrete action and resource, and the word "several ... together" distinguishes it from the single-item siblings create_esim_order and create_proxy_order. The return surface (one payment_url for the whole total, a reference and status_url per item) is stated up front, so an agent can identify the tool 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?

It routes follow-up explicitly ("Poll get_cart_status with reference and status_token") and explains the workflow boundary ("This does not charge anyone. After a verified payment, details for each item arrive by email and on its order page"). It never states when to prefer create_esim_order or create_proxy_order instead, i.e. the single-item case, so one exclusion is left to inference.

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?