Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_transaction_lookup

nansen_transaction_lookup
Read-onlyIdempotent

Look up one transaction by hash with its token transfers, values and labelled from/to addresses. Ethereum and Robinhood only (not Solana). 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
chainYes
block_timestampNoBlock time if known (ISO 8601); speeds up the lookup
transaction_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the cost ('1 credit') and the supported-chain boundary. It does not mention failure behavior for unknown hashes or unindexed chains, which would have pushed this higher.

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 compact sentences, front-loaded with what the tool returns, then the chain restriction, then the cost. Every clause carries information and nothing is repeated from the schema.

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 no output schema, the description usefully enumerates the return contents (transfers, values, labelled addresses), and the cost plus chain limits round it out. The only real gap is the optional block_timestamp parameter and error behavior, both minor for a simple single-record lookup.

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 only 33%, so the description must carry more weight; it covers the transaction hash and the chain constraint, but says nothing about the optional block_timestamp hint (only the schema explains that). The added meaning is therefore partial, leaving one of three parameters undocumented in the description.

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 names a specific verb and resource ('look up one transaction by hash') and immediately scopes the payload: token transfers, values, and labelled from/to addresses. It also bounds the tool by chain ('Ethereum and Robinhood only (not Solana)'), which an agent can use to rule it out for other networks without opening the 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?

Usage is clearly implied by 'one transaction by hash' plus the explicit chain exclusion, so an agent knows this is a single-hash lookup rather than a bulk or address-based query. It stops short of naming a sibling alternative for Solana or bulk-transfer needs, so it is clear context without explicit routing.

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