thru-mcp-server

Get account

get_account

Read-only

Fetch a Thru account by public key to retrieve its balance, nonce, owner program, size, and flags. Balances are raw integer strings.

Instructions

Look up a Thru account by public key and return its balance, nonce, owner program, size and flags. Balances are returned as raw integer strings.

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": {
      "address": "<address>"
    },
    "name": "get_account"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Account public key: a `ta…` Thru address (46 chars) or a 64-character hex-encoded pubkey.
`includeData`	No	Include the account's raw data blob as hex. Off by default because program accounts can be large.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, and the description adds a useful behavioral detail: balances are returned as raw integer strings, which is important for numeric handling. It doesn't describe error cases or includeData behavior, but the schema covers includeData, so this is an acceptable level of transparency.

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?

Two concise sentences, front-loaded with the action and resource, no redundant wording. Every sentence earns its place.

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?

Given the tool's simplicity (2 params, no output schema), the description adequately covers what the tool does and what it returns. The annotations cover safety, and the schema covers parameter details, so combined with the description, it is complete for an agent to select and invoke 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?

Schema description coverage is 100% for both parameters (address and includeData), so the description doesn't need to add extra semantics. The mention of 'public key' aligns with the schema's address description but adds no new information.

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?

The description clearly states the tool's purpose: looking up a Thru account by public key and returning specific fields (balance, nonce, owner program, size, flags). It distinguishes itself from sibling tools like get_transaction or get_network_status by focusing on account-level data.

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?

Provides clear context for when to use: whenever you need account details by public key. It does not explicitly mention exclusions or alternatives, but the sibling list and specific wording make the usage context obvious.

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

Deploy Server