Bitquery: Crypto & Blockchain Data

Tron Address Profile

tron_address_profile

Read-only

Tron (trx, TRX, TRON) address STATISTICS — successful transfer counts out/in and distinct counterparties. Triage an address during tracing. For one-call triage that ALSO returns the top counterparties, prefer tron_address_flow_summary. Role from the ratio: senders ≫ receivers = consolidator / sweep; receivers ≫ senders = distributor; ~1↔1 = relay (layering); thousands of both = mega-hub (exchange / treasury — don't trace deeper). No outgoing transfers at all = receive-only and no incoming = send-only, not a consolidator / distributor. First_Sent / Last_Sent / First_Received / Last_Received = first and last transfer in each direction. Bound a period with after_time / before_time; restrict to one token with contract (or currency) to also get Sent_Amount / Received_Amount in that token's units - without a token filter the amounts are NULL, because different tokens cannot be added. currency / contract (like after_time / before_time) narrow EVERY count, time and amount here - unlike tron_address_flow_summary, whose profile counts always cover all tokens. The counts are the transfers OF THIS ADDRESS itself. A bot account signs its transactions while a contract it controls holds and moves the tokens - the contract its transactions go TO, or a separate one - so a very active trading account can show few or no outgoing transfers here. To find the address that really moves its tokens, open one of its transaction hashes (for example a Tx_Hash from trader_trades) with tron_tx_transfers, then trace that address (tron_contract_creator with creator set to this account lists the contracts it deployed).

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

Input Schema

Name	Required	Description	Default
`format`	No	Shape of the returned data. "rows" (the default) returns one item per row. "columnar" returns a single item, {"columns":[...],"rows":[[value,...],...]}, naming the columns once and listing each row's values in that order; it is more compact for large results and carries the same values.	rows
`address`	Yes	Tron base58 address (T...).
`contract`	No	Restrict every figure to ONE exact token by its contract address (base58, starts with T) and return Sent_Amount / Received_Amount in that token's units. Empty = all tokens.
`currency`	No	Restrict every figure to one currency symbol (e.g. "USDT") and return Sent_Amount / Received_Amount. A symbol is NOT unique - clone tokens reuse it; pin the real token with contract. Empty = all tokens. No backslashes.
`after_time`	No	Only transfers at/after this UTC time - every count, time and amount covers that period. Empty = whole history. Format: YYYY-MM-DD, YYYY-MM-DD HH:MM[:SS], ISO-8601 like 2026-09-20T00:00:00Z (fraction or +02:00 offset allowed) or 10-digit unix seconds.
`before_time`	No	Only transfers strictly before this UTC time. Empty = up to now. Format: YYYY-MM-DD, YYYY-MM-DD HH:MM[:SS], ISO-8601 like 2026-09-20T00:00:00Z (fraction or +02:00 offset allowed) or 10-digit unix seconds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / format

Added value: +{
+  "default": "rows",
+  "description": "Shape of the returned data. \"rows\" (the default) returns one item per row. \"columnar\" returns a single item, {\"columns\":[...],\"rows\":[[value,...],...]}, naming the columns once and listing each row's values in that order; it is more compact for large results and carries the same values.",
+  "type": "string"
+}

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark it read-only and non-destructive, but the description adds substantial behavioral context: counts reflect only the address's own transfers, token filters change amount availability, amounts are NULL without a token filter, and time/token filters narrow every figure. It also warns about bot-controlled contract accounts where the real token movement may be hidden.

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?

The description is dense and lengthy, but it is front-loaded with the core purpose and alternative before diving into interpretation rules. Every sentence adds practical guidance for a complex tracing tool, though tighter formatting or shorter phrasing could improve scanability.

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 six-parameter tracing tool with no output schema, the description is unusually complete: it explains the returned time/count fields, amount behavior, filter effects, interpretation heuristics, and what to do when the address itself appears inactive. It covers both correct invocation and correct interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful interaction semantics beyond the schema: contract/currency restrict every count and enable Sent_Amount/Received_Amount, while after_time/before_time bound the entire profile. It also explains why amounts are NULL without a token filter and why currency symbols alone may be ambiguous.

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 states a specific resource and metric set: Tron address statistics with successful transfer counts in/out and distinct counterparties, explicitly framed for triage. It distinguishes itself from the named sibling tron_address_flow_summary, so an agent can tell the two apart 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 Guidelines5/5

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

It gives explicit usage guidance ('Triage an address during tracing') and names the alternative for one-call triage that also returns top counterparties. It further explains how to interpret ratios and edge cases (no outgoing vs no incoming), which directly supports tool selection and follow-up behavior.

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

All Bitquery: Crypto & Blockchain Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.