Skip to main content
Glama

YRUZ Solana Transaction Explain (0.003 USDC)

solana_tx_explain
Read-onlyIdempotent

Decode any Solana transaction into plain language: type (swap, transfer, NFT sale, mint ...), the program or DEX used, who sent what to whom with token symbols and amounts, SOL balance changes, fee and status. Lets an agent confirm a payment or audit what a wallet did. Price: 0.003 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"solana_tx_explain"}. Same tool over HTTP: https://yruz.one/api/crypto/tx?signature=kR2EnMwjxxQ3LrZD8fp1e5m6rkkMmDateF5bktxhJDaBaKE6NoP623PbNxjwDVxozQMcgGacBqTEkjrPLzk5TWc

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": {
      "signature": "<signature>"
    },
    "name": "solana_tx_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYestransaction signature (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / signature / examples
      Added value: +[
      +  "kR2EnMwjxxQ3LrZD8fp1e5m6rkkMmDateF5bktxhJDaBaKE6NoP623PbNxjwDVxozQMcgGacBqTEkjrPLzk5TWc"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial behavioral context the schema can't: per-call price, x402 payment flow with no account/API key, invalid input refused before payment, failed runs never charged, and that no payment yields a PaymentRequired response.

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?

Front-loaded with the core decode capability, then payment terms, then call guidance. Dense but each clause carries information; the inline example signature URL is the only slightly expendable element.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description covers what is returned, the payment/error semantics, and how to invoke it, and annotations carry the safety profile. An agent has everything needed to call it correctly.

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?

Only one parameter with 100% schema coverage that already documents 'signature (required)' with an example. The description's sample signature in the URL adds marginal context but no syntax or format guidance beyond the schema, so 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 ('Decode') and resource ('any Solana transaction') and enumerates concrete outputs: type, program/DEX, transfers with symbols/amounts, SOL balance changes, fee and status. An agent can distinguish it from solana_portfolio or solana_token_check 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?

Gives explicit use cases ('confirm a payment or audit what a wallet did') and routing hints ('get_example', HTTP endpoint). Lacks explicit exclusions naming sibling tools (e.g., when to prefer solana_portfolio), so it's clear context but not full when/when-not guidance.

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.