Gate Info MCP

info_onchain_get_address_transactions

Read-onlyIdempotent

Paginated transfers; BTC items include inputs/outputs/tx_status. partial_upstream_response when upstream total>0 but list unparseable. Chain aliases same as get_address_info. Profile→get_address_info. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Chain id (eth, trx, bsc, btc, sol, base, arb, ...); default eth.
`limit`	No	Max rows; default 20, max 400; maps to explorer page_size. Some filters apply only to GET list paths.
`address`	Yes	On-chain address.
`tx_type`	No	transfer \| contract_call \| token_transfer \| all (default).
`end_time`	No	End Unix seconds.
`start_time`	No	Start Unix seconds; pair with end_time; absolute wins over time_range.
`time_range`	No	Relative window vs start/end: 1h\|24h\|1d\|7d\|30d\|90d as [now-Δ, now]. Ignored if start_time or end_time set.
`to_address`	No	Filter recipient; maps to explorer GET to or POST body to. BlockInfo path ignores.
`from_address`	No	Filter sender; maps to explorer GET from or POST transfers from. BlockInfo path ignores.
`min_value_usd`	No	If >0, keep rows with value_usd >= threshold (same semantics as get_address_info min_value_usd). May map to explorer query when supported.
`nonzero_value`	No	If true, drop zero-amount token_transfer rows; passes nonzero_value to explorer POST when used.
`upstream_raw_mode`	No	off (default) \| lite \| full. Prefer off for public MCP. include_upstream_raw=true forces full.
`include_upstream_raw`	No	Prefer false (default). If true, include new_explorer_address_*_raw and per-item source_raw; large payload, not for public clients.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`count`	Yes
`items`	Yes
`limit`	No
`total`	Yes
`address`	Yes
`sources`	No
`tx_type`	Yes
`end_time`	No
`start_time`	No
`time_range`	No
`duration_ms`	Yes
`data_quality`	No
`transactions`	Yes
`min_value_usd`	No
`nonzero_value`	No
`quality_reasons`	No
`new_explorer_address_transfers_raw`	No
`new_explorer_address_transactions_raw`	No
`new_explorer_address_token_transfers_raw`	No
`new_explorer_address_sol_transactions_raw`	No
`new_explorer_address_internal_transactions_raw`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed43 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / items / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / items / items / properties / inputs / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / items / items / properties / inputs / items / properties / addresses / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / items / items / properties / inputs / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / items / items / properties / outputs / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / items / items / properties / outputs / items / properties / addresses / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / items / items / properties / outputs / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / items / items / properties / source_raw
```
Previous value: -trueNew value: +{
+  "items": {
+    "maximum": 255,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
```
- addedOutput schema / properties / items / items / properties / token / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / items / items / properties / token / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- changedOutput schema / properties / items / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- removedOutput schema / properties / new_explorer_address_internal_transactions_raw / anyOf
```
Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / new_explorer_address_internal_transactions_raw / items
```
Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / new_explorer_address_internal_transactions_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
- removedOutput schema / properties / new_explorer_address_sol_transactions_raw / anyOf
```
Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / new_explorer_address_sol_transactions_raw / items
```
Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / new_explorer_address_sol_transactions_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
- removedOutput schema / properties / new_explorer_address_token_transfers_raw / anyOf
```
Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / new_explorer_address_token_transfers_raw / items
```
Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / new_explorer_address_token_transfers_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
- removedOutput schema / properties / new_explorer_address_transactions_raw / anyOf
```
Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / new_explorer_address_transactions_raw / items
```
Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / new_explorer_address_transactions_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
- removedOutput schema / properties / new_explorer_address_transfers_raw / anyOf
```
Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / new_explorer_address_transfers_raw / items
```
Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / new_explorer_address_transfers_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / quality_reasons / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / sources / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / sources / items / properties / code / type
```
Previous value: -"integer"New value: +[
+  "null",
+  "integer"
+]
```
- changedOutput schema / properties / sources / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / transactions / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / transactions / items / properties / inputs / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / transactions / items / properties / inputs / items / properties / addresses / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / transactions / items / properties / inputs / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / properties / transactions / items / properties / outputs / items / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / transactions / items / properties / outputs / items / properties / addresses / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / transactions / items / properties / outputs / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- changedOutput schema / properties / transactions / items / properties / source_raw
```
Previous value: -trueNew value: +{
+  "items": {
+    "maximum": 255,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
```
- addedOutput schema / properties / transactions / items / properties / token / additionalProperties
```
Added value: +false
```
- changedOutput schema / properties / transactions / items / properties / token / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- changedOutput schema / properties / transactions / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```

Changed2 schema fields changedAug 7, 2026

changedInput schema / properties / include_upstream_raw / description

Previous value: -"If true, include new_explorer_address_*_raw and per-item source_raw; large payload. Default false."New value: +"Prefer false (default). If true, include new_explorer_address_*_raw and per-item source_raw; large payload, not for public clients."

changedInput schema / properties / upstream_raw_mode / description

Previous value: -"off (default) | lite (per-item source_raw) | full (page + item raw). include_upstream_raw=true forces full."New value: +"off (default) | lite | full. Prefer off for public MCP. include_upstream_raw=true forces full."

Changed6 schema fields changedJun 3, 2026

addedOutput schema / properties / items / items / properties / inputs

Added value: +{
+  "items": {
+    "properties": {
+      "addresses": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": "string"
+      },
+      "value_usd": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / items / items / properties / outputs

Added value: +{
+  "items": {
+    "properties": {
+      "addresses": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": "string"
+      },
+      "value_usd": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / items / items / properties / tx_status
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / transactions / items / properties / inputs

Added value: +{
+  "items": {
+    "properties": {
+      "addresses": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": "string"
+      },
+      "value_usd": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / transactions / items / properties / outputs

Added value: +{
+  "items": {
+    "properties": {
+      "addresses": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "value": {
+        "type": "string"
+      },
+      "value_usd": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / transactions / items / properties / tx_status
```
Added value: +{
+  "type": "string"
+}
```

First observedApr 16, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds specific behavioral details: 'partial_upstream_response when upstream total>0 but list unparseable' and 'BTC items include inputs/outputs/tx_status'. It also includes disclaimers like 'No account access, no order placement or fund transfers' which reinforce the read-only nature but add little beyond annotations. Overall, it adds some edge-case context and per-chain behavior, but not deeply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is about 55 words and includes several short declarative sentences. It front-loads the core purpose and includes useful edge-case info. However, it contains somewhat lengthy disclaimers ('No account access... Not investment advice') that, while harmless, are not central to invoking the tool and could be trimmed. The structure is acceptable but not maximally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters and an output schema exists, the description need not detail return values. It covers a key edge case (partial_upstream_response), BTC specifics, and cross-references for chain aliases and profile usage. However, it does not clarify pagination mechanics (e.g., cursor vs. offset) beyond 'paginated', nor does it state explicitly what types of transactions are included (transfers only vs. all tx types). It is adequate but has noticeable gaps for a complex tool.

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%, so parameters like chain, tx_type, time_range, and filters are already documented. The description adds 'Chain aliases same as get_address_info', which could clarify chain naming conventions, but the schema already lists examples and open-ended dots. No additional parameter semantics beyond the schema are provided, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Paginated transfers' as the core action, implying retrieval of address transactions. It also specifies BTC-specific data ('inputs/outputs/tx_status'), which adds nuance. However, it does not explicitly name 'transactions' beyond the tool name, and it omits mentioning that tx_type can be 'contract_call' or 'token_transfer', so the purpose is clear but not fully exhaustive.

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

Usage Guidelines3/5

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

The description provides a pointer to a sibling: 'Profile→get_address_info' suggests using get_address_info for profile queries, implicitly indicating this tool is for transactions. It also mentions 'Chain aliases same as get_address_info' for reuse. However, it does not explicitly state when to prefer this tool over other on-chain tools (e.g., get_transaction or get_token_onchain) nor give exclusions. The guidance is implied rather than explicit.

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

All Gate Info MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct data object and action (e.g., coin info vs rankings, market snapshot vs batch, marketdetail kline vs markettrend kline), with prefixes and descriptions clearly separated by domain. No two tools appear to serve the same purpose.

Naming Consistency5/5

All tools follow a consistent pattern: info_<domain>_<verb>_<object>, with verbs mainly get, search, and batch. The naming style is uniform across all 32 tools, making it easy to infer tool purpose from its name.

Tool Count3/5

32 tools is heavy compared to typical servers, and it exceeds the 25-tool threshold. However, the server is a comprehensive crypto data aggregator covering multiple subdomains (coin, macro, market, onchain, platform metrics), which justifies the large count to some extent. It sits at the borderline between borderline and too many.

Completeness5/5

The tool surface covers the full lifecycle for read-only research: coin discovery, rankings, search, technical analysis, onchain exploration, platform metrics, stablecoins, yield pools, bridges, and macro indicators. No critical missing functionality for the stated purpose of public research data access.

info_onchain_get_address_transactions

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources