Skip to main content
Glama

Wallet Doctor

txtrace

Read-only

Solana transaction trace: status, slot, fee, SOL balance changes, first 20 log lines — $0.0005 USDC per call via x402 v2 (Solana or Base).

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": "txtrace"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior, but the description adds genuinely non-derivable traits: a per-call price ($0.0005 USDC), the x402 v2 payment path on Solana or Base, and an output truncation limit (only the first 20 log lines). It stops short of explaining payment-failure behavior or whether failed/not-found transactions still incur the charge.

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 front-loaded sentence with the resource first, return contents second, and pricing last — no filler, nothing repeated from structured fields.

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 one-parameter read-only tool with no output schema, the description covers what comes back (including the log-line cap) and what it costs, which is what an agent needs to decide and pay. The main omission is signature format, which neither schema nor description supplies.

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 0% for the single required 'signature' parameter, so the description carries some burden; it implies the input is a transaction rather than an account, but never states the expected encoding/format (base58 transaction signature). Adequate but with a real gap.

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 resource (a Solana transaction) and action (trace) and then enumerates exactly what is returned: status, slot, fee, SOL balance changes, and the first 20 log lines. That enumeration makes it readily distinguishable from siblings like balance, approvals, drainForensics, and tokenSafety, which cover different resources.

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

Usage Guidelines2/5

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

It implies you call it with a transaction signature to inspect one transaction, but gives no explicit when-to-use/when-not-to-use guidance and never routes the agent to an alternative for related questions (e.g., account-level history vs. forensic analysis). The only selection aid is the cost line.

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