Skip to main content
Glama
Sign In

Xpress Flow Systems

by ng.com.xpressflowsystems.www
OverviewDiscussionsAdmin

create_proxy_order

Start a proxy purchase for a person. This does not charge anyone: it returns payment_url for the person to pay, in US dollars outside Nigeria and in naira in Nigeria. After a verified payment the proxies arrive by email and on the order page. Poll get_order_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": {
      "product": "<product>",
      "gb": "<gb>",
      "offer_id": "<offer_id>",
      "email": "<email>",
      "accept_terms": "<accept_terms>"
    },
    "name": "create_proxy_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbYesPack size (GB, or Mbps for a speed tier).
emailYesRequired: the person's email, for their receipt and order details (the lines).
countryNoOptional: the payer's two-letter country. Outside Nigeria (NG) they pay in US dollars. Defaults to where the request comes from.
productYesProduct id from list_proxy_products.
currencyNoOptional: USD or NGN. By default prices are in US dollars outside Nigeria and in naira inside Nigeria, from where the request comes from.
offer_idYesoffer_id of the pack from list_proxy_products.
accept_termsYesSet true only if your user agreed to the Terms of Use and Privacy Policy on this website.
target_countryNoOptional: two-letter target country from this pack's locations.countries. Omit only for Network default, which does not guarantee a country. This is separate from the payer country.
email_verification_tokenNoverification_token from verify_email_code for this email (required while email checks are on).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_country / description
      Previous value: -"Optional: two-letter country the proxy lines should exit from."New value: +"Optional: two-letter target country from this pack's locations.countries. Omit only for Network default, which does not guarantee a country. This is separate from the payer country."
  2. Changed1 schema field changed
    • changedInput schema / properties / target_country / description
      Previous value: -"Optional: two-letter target country from this pack's locations.countries. Omit only for Network default, which does not guarantee a country. This is separate from the payer country."New value: +"Optional: two-letter country the proxy lines should exit from."
  3. Changed1 schema field changed
    • changedInput schema / properties / target_country / description
      Previous value: -"Optional: two-letter country the proxy lines should exit from."New value: +"Optional: two-letter target country from this pack's locations.countries. Omit only for Network default, which does not guarantee a country. This is separate from the payer country."
  4. Changed1 schema field changed
    • addedInput schema / properties / email_verification_token
      Added value: +{
+  "description": "verification_token from verify_email_code for this email (required while email checks are on).",
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Optional: the person's email, for the receipt and the lines."New value: +"Required: the person's email, for their receipt and order details (the lines)."
    • changedInput schema / required
      Previous value: -[
-  "product",
-  "gb",
-  "offer_id",
-  "accept_terms"
-]New value: +[
+  "product",
+  "gb",
+  "offer_id",
+  "email",
+  "accept_terms"
+]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-idempotent and open-world. The description adds substantial context beyond that: no charge occurs, a payment_url is returned, currency depends on payer country, and proxies are delivered by email and on the order page only after a verified payment. It stops short of describing what the response object contains (e.g., whether reference and status_token are returned in the payload).

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?

Four short sentences, front-loaded with purpose then the high-value 'does not charge anyone' clarification, then delivery behavior, then the required next step. No filler and no repetition of schema documentation.

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 9-parameter mutation with no output schema, the description covers the essential agent-relevant facts: no immediate charge, where the payment URL comes from, conditional currency, and how to confirm the outcome. It omits the email verification prerequisite described only in the schema, but that gap is minor since the schema covers it.

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 parameters (including currency, country, target_country, email_verification_token) are already fully documented. The description restates the USD-outside-Nigeria / NGN-inside-Nigeria rule that the currency and country fields already carry, adding little new meaning. Baseline 3 applies.

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 ('Start a proxy purchase for a person') and immediately implies the sibling distinction from create_cart_order, create_domain_order and create_esim_order by naming the resource. An agent can select it without opening any 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?

Gives clear use context and a follow-up path: after starting, poll get_order_status with reference and status_token. It does not explicitly say when NOT to use this versus the other create_* tools, but the resource-specific framing makes the boundary implicit and unambiguous.

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 toolsInspect
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