Teardrop

Get Transaction

get_transaction

Read-only

Get details and receipt for an Ethereum or Base transaction by hash. Includes bounded calldata, normalized event logs, transaction index, and receipt-derived effective gas price and fee when available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tx_hash`	Yes	Transaction hash (0x…)
`chain_id`	No	Chain ID (1=Ethereum, 8453=Base)

Output Schema

TableJSON Schema

Name	Required	Description
`logs`	No
`status`	No	1=success, 0=revert, None=pending
`fee_eth`	No
`fee_wei`	No
`tx_hash`	Yes
`chain_id`	Yes
`gas_used`	Yes
`value_eth`	Yes
`input_data`	No	Hex calldata, bounded to 8 KiB
`to_address`	Yes
`block_number`	Yes
`from_address`	Yes
`gas_price_gwei`	Yes
`logs_truncated`	No
`transaction_index`	No
`input_data_truncated`	No
`effective_gas_price_gwei`	No

Schema Changelog

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

Changed10 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```
addedInput schema / properties / tx_hash / title
```
Added value: +"Tx Hash"
```

addedInput schema / title

Added value: +"mcp_get_transactionArguments"

addedOutput schema / $defs

Added value: +{
+  "TransactionLog": {
+    "properties": {
+      "address": {
+        "title": "Address",
+        "type": "string"
+      },
+      "data": {
+        "title": "Data",
+        "type": "string"
+      },
+      "data_truncated": {
+        "default": false,
+        "title": "Data Truncated",
+        "type": "boolean"
+      },
+      "log_index": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Log Index"
+      },
+      "topics": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Topics",
+        "type": "array"
+      },
+      "topics_truncated": {
+        "default": false,
+        "title": "Topics Truncated",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "address",
+      "topics",
+      "data"
+    ],
+    "title": "TransactionLog",
+    "type": "object"
+  }
+}

addedOutput schema / properties / logs / items / $ref
```
Added value: +"#/$defs/TransactionLog"
```

removedOutput schema / properties / logs / items / properties

Removed value: -{
-  "address": {
-    "title": "Address",
-    "type": "string"
-  },
-  "data": {
-    "title": "Data",
-    "type": "string"
-  },
-  "data_truncated": {
-    "default": false,
-    "title": "Data Truncated",
-    "type": "boolean"
-  },
-  "log_index": {
-    "anyOf": [
-      {
-        "type": "integer"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Log Index"
-  },
-  "topics": {
-    "items": {
-      "type": "string"
-    },
-    "title": "Topics",
-    "type": "array"
-  },
-  "topics_truncated": {
-    "default": false,
-    "title": "Topics Truncated",
-    "type": "boolean"
-  }
-}

removedOutput schema / properties / logs / items / required

Removed value: -[
-  "address",
-  "topics",
-  "data"
-]

removedOutput schema / properties / logs / items / title
```
Removed value: -"TransactionLog"
```
removedOutput schema / properties / logs / items / type
```
Removed value: -"object"
```

Changed8 schema fields changedAug 11, 2026

addedOutput schema / properties / effective_gas_price_gwei

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Effective Gas Price Gwei"
+}

addedOutput schema / properties / fee_eth

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fee Eth"
+}

addedOutput schema / properties / fee_wei

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Fee Wei"
+}

addedOutput schema / properties / input_data

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hex calldata, bounded to 8 KiB",
+  "title": "Input Data"
+}

addedOutput schema / properties / input_data_truncated

Added value: +{
+  "default": false,
+  "title": "Input Data Truncated",
+  "type": "boolean"
+}

addedOutput schema / properties / logs

Added value: +{
+  "items": {
+    "properties": {
+      "address": {
+        "title": "Address",
+        "type": "string"
+      },
+      "data": {
+        "title": "Data",
+        "type": "string"
+      },
+      "data_truncated": {
+        "default": false,
+        "title": "Data Truncated",
+        "type": "boolean"
+      },
+      "log_index": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Log Index"
+      },
+      "topics": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Topics",
+        "type": "array"
+      },
+      "topics_truncated": {
+        "default": false,
+        "title": "Topics Truncated",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "address",
+      "topics",
+      "data"
+    ],
+    "title": "TransactionLog",
+    "type": "object"
+  },
+  "title": "Logs",
+  "type": "array"
+}

addedOutput schema / properties / logs_truncated

Added value: +{
+  "default": false,
+  "title": "Logs Truncated",
+  "type": "boolean"
+}

addedOutput schema / properties / transaction_index

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Transaction Index"
+}

First observedJul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: it includes specific fields like bounded calldata and normalized event logs, and notes the fee is included 'when available', indicating conditional behavior. This goes beyond merely restating 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?

Two tightly packed sentences with no filler. Each clause adds value: the first defines the core action and scope, the second lists key return fields and conditional behavior. Excellent structure for quick comprehension.

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?

The description covers the purpose, scope, and key output details, and the output schema exists to define return structure. It lacks error behavior or prerequisites, but for a simple read tool with full annotations and an output schema, it is sufficiently complete to guide an agent.

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?

Input schema covers 100% of parameters with descriptions (tx_hash format, chain_id with Ethereum/Base values). The description provides no additional parameter-level semantics beyond what the schema already states, so it rests at the baseline for full 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 states a specific verb ('Get'), a specific resource ('details and receipt for an Ethereum or Base transaction by hash'), and enumerates distinctive outputs (bounded calldata, normalized event logs, transaction index, effective gas price). This clearly distinguishes it from siblings like decode_transaction.

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 implies usage (when you have a transaction hash and need details/receipt) but does not explicitly state when to use this tool over alternatives, nor does it provide exclusions. The sibling decode_transaction could benefit from a note, but the context is not misleading.

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

All Teardrop 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

A3.7/5.0

Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources

Need Help?