---
title: Tools Reference
description: Arguments, limits, and usage for each read-only tool on the Thru
  MCP server at mcp.thru.org.
source_url:
  html: https://thru.org/docs/api-ref/thru-mcp/tools-reference/
  md: https://thru.org/docs/api-ref/thru-mcp/tools-reference.md
---

# Tools Reference

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](https://thru.org/docs/api-ref/thru-mcp/overview.md).

## Tool Map

| Tool | Arguments | Best for |
| - | - | - |
| `get_block` | `slot`, optional `network` | Inspecting one block: producer, timestamp, status, compute use, and transactions. |
| `get_transaction` | `signature`, optional `network` | Debugging one transaction: status, fee, accounts, decoded instruction, and events. |
| `get_account` | `address`, optional `network` | Reading account balance, owner, flags, and data size. |
| `list_account_transactions` | `address`, optional `pageSize`, `pageToken`, `network` | Walking an account’s transaction history page by page. |
| `list_recent_blocks` | optional `limit`, `network` | Seeing the latest slots on a network. |
| `list_recent_transactions` | optional `limit`, `network` | Seeing the latest transactions across recent blocks. |
| `search` | `query`, optional `network` | Finding out whether a value is a slot, signature, or address, and which tool reads it. |
| `get_program_abi` | `program`, optional `network` | Fetching a program’s on-chain ABI with its instruction and event definitions. |
| `open_explorer_link` | `url` | Reading the block, transaction, or account behind a `scan.thru.org` link. |

All tools are read-only and idempotent.

## Shared Arguments

- **`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](https://thru.org/docs/api-ref/thru-mcp/overview.md#networks) and [Explorer Links](https://thru.org/docs/api-ref/thru-mcp/overview.md#explorer-links) for the rules.

## Returned Shape

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](https://thru.org/docs/api-ref/thru-mcp/overview.md#responses-and-errors).

## Tool Details

### `get_block`

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

| Argument | Type | Notes |
| - | - | - |
| `slot` | integer or string | A slot number, or a block link such as `https://scan.thru.org/block/12345?network=betanet`. |
| `network` | string, optional | `betanet`. |

```json
{ "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

### `get_transaction`

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

| Argument | Type | Notes |
| - | - | - |
| `signature` | string | A `ts...` signature, or a transaction link such as `https://scan.thru.org/tx/ts...`. |
| `network` | string, optional | `betanet`. |

```json
{ "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.

### `get_account`

Use when you need current account metadata.

| Argument | Type | Notes |
| - | - | - |
| `address` | string | A `ta...` address, or an address link such as `https://scan.thru.org/address/ta...`. |
| `network` | string, optional | `betanet`. |

```json
{ "address": "ta..." }
```

This is the fastest way to inspect:

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

### `list_account_transactions`

Use when one account is the center of the investigation.

| Argument | Type | Notes |
| - | - | - |
| `address` | string | A `ta...` address or an address link. |
| `pageSize` | integer, optional | 1 to 100. Default 10. |
| `pageToken` | string, optional | `pagination.nextPageToken` from the previous call. |
| `network` | string, optional | `betanet`. |

```json
{ "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.

### `list_recent_blocks`

Use for a quick view of the latest slots.

| Argument | Type | Notes |
| - | - | - |
| `limit` | integer, optional | 1 to 50. Default 10. |
| `network` | string, optional | `betanet`. |

```json
{ "limit": 10 }
```

### `list_recent_transactions`

Use for a chain-wide feed of recent transactions.

| Argument | Type | Notes |
| - | - | - |
| `limit` | integer, optional | 1 to 50. Default 10. |
| `network` | string, optional | `betanet`. |

```json
{ "limit": 10, "network": "betanet" }
```

### `search`

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

| Argument | Type | Notes |
| - | - | - |
| `query` | string | A block number, `ts...` signature, `ta...` address, or explorer link. |
| `network` | string, optional | `betanet`. |

```json
{ "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.

### `get_program_abi`

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

| Argument | Type | Notes |
| - | - | - |
| `program` | string | A `ta...` program address or an address link. |
| `network` | string, optional | `betanet`. |

```json
{ "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.

### `open_explorer_link`

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.

| Argument | Type | Notes |
| - | - | - |
| `url` | string | `https://scan.thru.org/block/<slot>`, `/tx/<signature>`, or `/address/<address>`, with an optional `?network=betanet`. |

```json
{ "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.

## Recommended Usage Pattern

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
