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. Dates show when Glama detected each change.

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.3/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent aspects. The description adds valuable behavioral context: 'fields sparse if upstream thin' warns of incomplete data, and it reaffirms no account access or order placement. No contradiction with annotations.

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?

Three concise sentences front-load the core function, then add the token alternative, read-only restriction, and disclaimers. No wasted words; efficient and well-structured.

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 presence of an output schema and annotations, the description covers all necessary usage context: single transaction lookup, sparse-field behavior, the distinction from token tool, and safety boundaries. Nothing essential is missing for an agent to call it 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?

The input schema has 100% coverage for all four parameters, each with descriptive text. The description adds little beyond the schema for parameters; it only hints at sparse fields in the response, which is already noted in the schema for tx_hash. Baseline 3 is appropriate given high schema coverage.

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: retrieve one transaction by hash. It distinguishes itself from the token-view tool by explicitly pointing to get_token_onchain, making it unambiguous among siblings.

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?

It provides clear guidance for when to use this tool vs. the token alternative, and reinforces its read-only nature. It does not explicitly exclude other on-chain tools like get_address_transactions, but the single-transaction scope is evident.

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_transaction

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources