Skip to main content
Glama

X1 tx explain

x1_tx_explain
Read-onlyIdempotent

Decode and explain an X1 transaction signature in plain language with balance changes, programs called, and fees. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "sig": "<sig>"
    },
    "name": "x1_tx_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
sigYesX1 transaction signature (base58, 64 bytes)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description isn't burdened with safety disclosure. It nonetheless adds meaningful context the annotations can't: a concrete price ($0.003 per call), the accepted payment rails/assets (USDC on Arc/Base/Solana, XNT on X1), and the fact that payment settles inside the tool call. Failure modes (unpaid, insufficient funds, invalid signature) are not described.

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?

Three sentences, front-loaded with the purpose, then economics, then the call protocol. Every sentence carries information an agent needs. Slightly dense with parenthetical payment rails, but nothing is redundant.

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 only two parameters and no output schema, the description covers the essentials: what the decode returns, what it costs, and how the paid handshake works. It would be stronger with a note on what happens when the transaction signature is unknown or malformed, but nothing critical is absent for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so both params are already documented, establishing a baseline of 3. The description goes beyond that by explaining the sequencing semantics of `payment` — omit it first to get terms, return with the signed payload to complete the purchase — which the schema's phrasing only partially conveys.

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 opens with a specific verb pair and resource ("Decode and explain an X1 transaction signature") and enumerates what the agent gets back: balance changes, programs called, fees. It never distinguishes itself from the similar-looking sibling `tx_explain` or `evm_tx`, so an agent choosing between them gets no help, keeping this below a 5.

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?

Strong procedural guidance for the two-step paid flow: call once without `payment` to obtain terms, sign with your own wallet, call again with `payment` to complete. That is explicit and actionable. What's missing is when to prefer this over `tx_explain` or `evm_tx`, so the sibling-choice guidance is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources