Data Figure Studio

create_usdc_order

Create a USDC payment order on Solana or Ethereum, paid to the store wallet (fees ~$0 on Solana; buyer pays ETH gas on Ethereum). Returns payment instructions incl. a Solana Pay URL and reference.

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": {
      "chain": "<chain>",
      "pack": "<pack>"
    },
    "name": "create_usdc_order"
  }
}

Input Schema

Name	Required	Description	Default
`pack`	Yes	p1 = 1 figure 0.20 USDC (agent rate), paper = 12 figures 5 USDC, year = 100 figures 30 USDC, team = 500 figures 100 USDC, lab = 1000 figures 150 USDC
`chain`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / pack / description

Previous value: -"p1 = 1 figure 0.20 USDC (agent rate), paper = 12 figures 7 USDC, year = 200 figures 79 USDC, lab = 1000 figures 249 USDC"New value: +"p1 = 1 figure 0.20 USDC (agent rate), paper = 12 figures 5 USDC, year = 100 figures 30 USDC, team = 500 figures 100 USDC, lab = 1000 figures 150 USDC"

changedInput schema / properties / pack / enum

Previous value: -[
-  "p1",
-  "paper",
-  "year",
-  "lab"
-]New value: +[
+  "p1",
+  "paper",
+  "year",
+  "team",
+  "lab"
+]

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses cost traits and what is returned (payment instructions, Solana Pay URL, reference), but for a state-mutating create tool it omits whether the order expires, whether repeated calls are idempotent, and any auth or wallet requirements.

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?

A single front-loaded sentence covering action, chains, destination, cost, and return payload with no filler. The parenthetical is dense but reads cleanly; two sentences would have made the return clause easier to scan.

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?

Only two required params and no output schema, so the description's explanation of the return payload (Solana Pay URL + reference) is genuinely needed and present. Remaining gaps around order lifetime and idempotency are the main shortfall for a payment-creation tool.

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 50%: 'pack' is exhaustively documented in-schema while 'chain' has no description at all. The description partly compensates by linking chain choice to fee/gas behavior, but it adds nothing about pack semantics or pricing tiers beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 a USDC payment order') and narrows it by chain ('on Solana or Ethereum') and payout destination ('paid to the store wallet'). It never names a sibling, so it doesn't explicitly separate itself from build_usdc_solana_tx or create_paypal_checkout.

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

Usage Guidelines3/5

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

The fee/gas parentheticals imply the choice between Solana (near-free) and Ethereum (buyer pays gas), which hints at when each chain is preferable. But there is no explicit statement of when to use this versus build_usdc_solana_tx or the PayPal checkout siblings, so routing 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 Data Figure Studio 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?