Skip to main content
Glama

Looking up transaction details

transaction_lookup
Read-onlyIdempotent

Get transaction details and token transfers for a transaction hash.

No contract function is shown. For it, use the Method column of address_transactions for the From address.

Returns a markdown table with transaction details and token transfers. Only EVM transaction hashes are supported.

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": {
      "transaction_hash": "<transaction_hash>"
    },
    "name": "transaction_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain network where the transaction occurred, such as ethereum or base. Use the chain shown with the transaction.all
transaction_hashYesEVM transaction hash from a block explorer or address_transactions. Use the transaction hash, not a wallet or token address.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / chain / description
      Added value: +"Blockchain network where the transaction occurred, such as ethereum or base. Use the chain shown with the transaction."
    • addedInput schema / properties / transaction_hash / description
      Added value: +"EVM transaction hash from a block explorer or address_transactions. Use the transaction hash, not a wallet or token address."
  2. Changed1 schema field changed
    • addedInput schema / properties / chain
      Added value: +{
      +  "default": "all",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed1 schema field changed
    • removedInput schema / properties / chain
      Removed value: -{
      -  "default": "ethereum",
      -  "type": "string"
      -}
  5. Changed1 schema field changed
    • addedInput schema / properties / chain
      Added value: +{
      +  "default": "ethereum",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real context: it discloses the return format (a markdown table with transaction details and token transfers) and a hard constraint that only EVM transaction hashes are supported, which annotations do not convey.

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?

Short and front-loaded with the core capability. The middle fragment 'No contract function is shown. For it, use...' is grammatically disjoint and takes a moment to decode, but there is no filler, and every sentence carries a distinct constraint.

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 annotations covering the safety profile, an output schema covering return values, and 100% schema coverage on inputs, the description only needs to add scope and limitations — which it does (EVM-only, table output, missing contract function). Pagination or result-size behavior is the only notable omission.

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 coverage is 100% and both parameters are fully documented in the schema, including the warning to pass a transaction hash rather than a wallet or token address and the chain guidance. The description adds essentially no parameter meaning beyond that, so the baseline 3 applies.

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 opens with a specific verb+resource+scope: 'Get transaction details and token transfers for a transaction hash.' It also explicitly scopes out what it does not return ('No contract function is shown'), which lets an agent separate it from address_transactions without opening either schema.

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 gives a clear use condition (you have a transaction hash) and names a fallback route when contract function data is needed — the Method column of address_transactions. The routing sentence is slightly awkward to parse, and it does not explicitly state when NOT to use it for non-EVM chains beyond the closing limitation note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources