Gate Info MCP

info_onchain_get_transaction

Read-onlyIdempotent

One transaction by hash; fields sparse if upstream thin. Token view→get_token_onchain. 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 e.g. eth, bsc, btc; default eth.
`tx_hash`	Yes	Transaction hash. Response may omit fields when upstream data is incomplete.
`upstream_raw_mode`	No	off (default) \| lite \| full. Prefer off for public MCP; only full adds detail raw. include_upstream_raw=true forces full.
`include_upstream_raw`	No	Prefer false (default). If true, include explorer_detail_raw and blockinfo_detail_raw; large payload, not for public clients.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No
`from`	No
`chain`	Yes
`value`	No
`tx_fee`	No
`sources`	No
`to_tags`	No
`tx_hash`	Yes
`tx_tags`	No
`gas_used`	No
`from_tags`	No
`value_usd`	No
`block_time`	No
`tx_fee_usd`	No
`duration_ms`	Yes
`method_name`	No
`block_height`	No
`contract_ret`	No
`data_quality`	No
`instructions`	No
`program_logs`	No
`quality_reasons`	No
`token_transfers`	No
`sol_balance_change`	No
`explorer_detail_raw`	No
`blockinfo_detail_raw`	No
`token_balance_change`	No
`internal_transactions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed30 schema fields changedAug 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / blockinfo_detail_raw / anyOf

Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / blockinfo_detail_raw / items

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / blockinfo_detail_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```

removedOutput schema / properties / explorer_detail_raw / anyOf

Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / explorer_detail_raw / items

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / explorer_detail_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```

changedOutput schema / properties / from_tags / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / from_tags / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / instructions / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / instructions / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / internal_transactions / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / internal_transactions / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / program_logs / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / program_logs / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / quality_reasons / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / sol_balance_change / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / sol_balance_change / 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"
+]

changedOutput schema / properties / to_tags / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / to_tags / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / token_balance_change / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / token_balance_change / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / token_transfers / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / token_transfers / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

changedOutput schema / properties / tx_tags / items

Previous value: -{
-  "anyOf": [
-    {
-      "type": "object"
-    },
-    {
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    },
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}New value: +true

changedOutput schema / properties / tx_tags / 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 explorer_detail_raw and blockinfo_detail_raw; large payload. Default false."New value: +"Prefer false (default). If true, include explorer_detail_raw and blockinfo_detail_raw; large payload, not for public clients."

changedInput schema / properties / upstream_raw_mode / description

Previous value: -"off (default) | lite | full; only full adds explorer/blockinfo detail raw. include_upstream_raw=true forces full."New value: +"off (default) | lite | full. Prefer off for public MCP; only full adds detail raw. include_upstream_raw=true forces full."

First observedApr 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate read-only/idempotent behavior; the description adds explicit constraints such as no account access and no fund transfers, plus a sparse-fields caveat. This goes beyond the annotation baseline.

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 short and mostly focused. The 'Token view→get_token_onchain' fragment is slightly cryptic but does not make the description bloated.

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

Completeness4/5

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

With a full output schema and complete parameter descriptions, the description is sufficient for correct invocation. It could more explicitly state when to prefer this over address-transaction tools, but that is not essential.

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 descriptions cover 100% of parameters, so the description does not need to add much. It reinforces the hash-based lookup but does not materially enhance parameter understanding.

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?

Clearly identifies retrieving a single transaction by tx_hash. The 'one transaction' wording distinguishes it from address transaction and token on-chain sibling tools.

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 useful context: read-only public research data, no account access, no order placement, and not investment advice. It does not explicitly compare against all sibling tools, but the token view pointer gives some direction.

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

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.