Data Figure Studio

build_usdc_solana_tx

Build the unsigned Solana USDC payment transaction for an order; the buyer signs and submits it with their wallet.

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": {
      "order_id": "<order_id>",
      "pack": "<pack>",
      "order_token": "<order_token>",
      "expires_at": "<expires_at>",
      "buyer": "<buyer>"
    },
    "name": "build_usdc_solana_tx"
  }
}

Input Schema

Name	Required	Description
`pack`	Yes
`buyer`	Yes	Buyer Solana address
`order_id`	Yes
`expires_at`	Yes
`order_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.2/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 burden, and it does disclose the most important non-obvious trait: the transaction is unsigned and the buyer, not this tool, submits it. It omits other behavioral facts an agent needs, such as what the return payload is, how order_token is validated, and what happens when expires_at has passed.

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?

A single well-formed sentence that front-loads the operation and its scope, with no filler. Nothing would be gained by adding more prose at this level of abstraction.

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

Completeness2/5

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

For a five-parameter, all-required transaction-building tool with no annotations, no output schema, and 20% parameter coverage, one sentence is insufficient. The agent still does not know the expected return format (serialized/encoded transaction, fee payer, blockhash freshness) or the expiry and token prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five required parameters with only 20% schema description coverage (just 'buyer'), and the description adds no parameter meaning at all beyond the generic phrase 'for an order'. pack, order_token, and expires_at are left entirely unexplained in both the schema and the description.

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?

States a specific verb and resource ('Build the unsigned Solana USDC payment transaction for an order'), which cleanly separates it from siblings like create_usdc_order and verify_usdc_order. It stops short of naming those siblings explicitly, so differentiation is implicit rather than stated.

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 description implies usage by tying the tool to 'an order' and describing the follow-on step (buyer signs and submits), which orients the agent in the order lifecycle. However, it gives no explicit when-to-use, when-not-to-use, or reference to an alternative sibling such as create_usdc_order or verify_usdc_order.

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?