Vike Data API

Transaction Lookup

transaction_lookup

Read-onlyIdempotent

What happened in one transaction, by hash: status (success, failed, pending; unknown for Ethereum transactions before October 2017), block, time, from and to (each with its label: entity, wallet_type, label_confidence), value (the chain's coin sent at the top level: amount in whole coins, amount_wei exact, amount_usd), fee (gas_used, gas price and the fee in the chain's coin) and token_transfers: every ERC-20 transfer in it with token_address, symbol, decimals, from and to (labelled), amount in whole tokens, amount_raw exact and amount_usd. usd_basis says how each USD value was priced: transfer_time (the price at the transaction's minute) or latest_daily_price (only for a transaction from the last 24 hours not priced yet); null = no price. NFT transfers and internal (contract-call) coin transfers are not listed. found is false when the hash does not exist on that chain: the same hash format is used on every EVM chain, so try the chain it was sent on. Use when the user pastes a transaction hash or asks 'what happened in this transaction' / 'did it go through'.

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

Input Schema

Name	Required	Description	Default
`chain`	No	Chain (default ethereum)	ethereum
`tx_hash`	Yes	Transaction hash: 0x followed by 64 hex characters

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: NFT transfers and internal coin transfers are excluded, pre-October-2017 Ethereum status is unknown, and `found=false` means the hash is not on that chain. The one gap is that it does not state pricing lag or latency expectations beyond the usd_basis note.

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?

Front-loaded with the core purpose, then a dense but ordered field-by-field enumeration, closing with usage triggers. Every clause carries information, though the single run-on paragraph makes it harder to scan; bullet-style grouping of value/fee/token_transfers would improve it.

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?

There is no output schema, so the description must document return values — and it does, covering status quirk, labelled addresses, value/fee breakdown, token transfers, usd_basis semantics, and the not-found case. Nothing essential for correct invocation or interpretation appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description exceeds that by explaining that the same hash format exists on every EVM chain and that a failed lookup should prompt trying the originating chain — meaningful semantics for the `chain` parameter. It still doesn't discuss the enum options individually, relying on the schema for that.

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?

Opens with a specific verb and resource ("What happened in one transaction, by hash") and immediately enumerates the exact response fields (status, block, time, from/to, value, fee, token_transfers). This clearly separates it from siblings like wallet_transactions or token_transfers, which operate at wallet- or token-level rather than a single hash.

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?

Gives explicit trigger conditions: a pasted transaction hash, or questions like "what happened in this transaction" / "did it go through". It also adds a recovery path when `found` is false (try the chain it was sent on). No sibling alternatives are named (e.g. wallet_transactions), so it stops short of full routing guidance.

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

All Vike Data API 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.