Skip to content

Tools Reference

View as Markdown

Use this page when your agent is connected to the Thru MCP and you need the exact tool and arguments to call. To connect an agent, see the Thru MCP Overview.

ToolArgumentsBest for
get_blockslot, optional networkInspecting one block: producer, timestamp, status, compute use, and transactions.
get_transactionsignature, optional networkDebugging one transaction: status, fee, accounts, decoded instruction, and events.
get_accountaddress, optional networkReading account balance, owner, flags, and data size.
list_account_transactionsaddress, optional pageSize, pageToken, networkWalking an account’s transaction history page by page.
list_recent_blocksoptional limit, networkSeeing the latest slots on a network.
list_recent_transactionsoptional limit, networkSeeing the latest transactions across recent blocks.
searchquery, optional networkFinding out whether a value is a slot, signature, or address, and which tool reads it.
get_program_abiprogram, optional networkFetching a program’s on-chain ABI with its instruction and event definitions.
open_explorer_linkurlReading the block, transaction, or account behind a scan.thru.org link.

All tools are read-only and idempotent.

  • network: betanet. When you omit it, the tool uses the explorer link’s ?network= if you passed a link, else the endpoint’s ?network=, else betanet. An explicit network must match the link’s network. open_explorer_link takes no network argument; it uses the link’s.
  • Addresses are Thru-format addresses such as ta....
  • Signatures are Thru-format signatures such as ts....
  • Slots are non-negative integers.
  • Explorer links: slot, signature, address, program, and query also accept a https://scan.thru.org/... link. The link must point at the page the tool expects; for example, get_block rejects a transaction link and names the right tool.
  • String arguments are limited to 2048 characters.

See Networks and Explorer Links for the rules.

Each tool returns one text item encoded as TOON, a compact form of JSON for language models, with three fields:

  • data: the structured result
  • summary: a one-line, plain-English description of the result
  • links: absolute explorer URLs, for example https://scan.thru.org/tx/<signature>?network=betanet

When the arguments are wrong, the tool returns isError: true and a message saying what to change. See Responses and Errors.

Use when you know the slot and want block-level context.

ArgumentTypeNotes
slotinteger or stringA slot number, or a block link such as https://scan.thru.org/block/12345?network=betanet.
networkstring, optionalbetanet.
{ "slot": 12345, "network": "betanet" }

Follow up with:

  • get_transaction for a signature listed in the block
  • list_recent_blocks if you only wanted the latest chain activity

Use when you want the full execution picture for one transaction.

ArgumentTypeNotes
signaturestringA ts... signature, or a transaction link such as https://scan.thru.org/tx/ts....
networkstring, optionalbetanet.
{ "signature": "ts..." }

This is usually the best tool for:

  • checking execution status and fee
  • inspecting read-write and read-only accounts
  • reading the decoded instruction
  • reading emitted events

Instructions and events are decoded with the program’s on-chain ABI when one is published.

Use when you need current account metadata.

ArgumentTypeNotes
addressstringA ta... address, or an address link such as https://scan.thru.org/address/ta....
networkstring, optionalbetanet.
{ "address": "ta..." }

This is the fastest way to inspect:

  • balance and owner
  • flags such as program, compressed, or ephemeral
  • data size

Use when one account is the center of the investigation.

ArgumentTypeNotes
addressstringA ta... address or an address link.
pageSizeinteger, optional1 to 100. Default 10.
pageTokenstring, optionalpagination.nextPageToken from the previous call.
networkstring, optionalbetanet.
{ "address": "ta...", "pageSize": 25 }

The result’s pagination holds pageSize, nextPageToken when more pages exist, and totalSize when the RPC reports it. Pass nextPageToken as pageToken to get the next page.

Use for a quick view of the latest slots.

ArgumentTypeNotes
limitinteger, optional1 to 50. Default 10.
networkstring, optionalbetanet.
{ "limit": 10 }

Use for a chain-wide feed of recent transactions.

ArgumentTypeNotes
limitinteger, optional1 to 50. Default 10.
networkstring, optionalbetanet.
{ "limit": 10, "network": "betanet" }

Use when you don’t know whether a value is a slot, signature, or address.

ArgumentTypeNotes
querystringA block number, ts... signature, ta... address, or explorer link.
networkstring, optionalbetanet.
{ "query": "ta..." }

search makes no RPC calls. Each result names its type, its explorer URL, and the tool call that reads it, for example get_account with { "address": "ta...", "network": "betanet" }. Make that call next.

Use when you need the ABI published on-chain for a deployed program.

ArgumentTypeNotes
programstringA ta... program address or an address link.
networkstring, optionalbetanet.
{ "program": "ta..." }

This is especially useful when:

  • checking that the published ABI matches the deployed program
  • debugging explorer reflection mismatches
  • reading instruction and event definitions without leaving the agent workflow

If the program has no published ABI, the tool returns a not-found error.

Use when someone shares a scan.thru.org link. Pass the link instead of fetching the page: explorer pages load their data in the browser, so a fetched page has no values.

ArgumentTypeNotes
urlstringhttps://scan.thru.org/block/<slot>, /tx/<signature>, or /address/<address>, with an optional ?network=betanet.
{ "url": "https://scan.thru.org/block/12345?network=betanet" }

The result is the same as get_block, get_transaction, or get_account for that entity. Links with ?rpc= or ?network=custom are rejected, because custom RPC links work only in the browser explorer.

To debug a deployed program:

  1. open_explorer_link if you were given an explorer link, or search if the identifier is ambiguous
  2. get_transaction for a failing or surprising transaction
  3. get_program_abi if the payload may be decoded against the wrong ABI
  4. get_account or list_account_transactions for account-level follow-up

To inspect recent network activity:

  1. list_recent_blocks or list_recent_transactions
  2. get_block or get_transaction for the item worth a closer look