Skip to main content
Glama

BRAINIAC Wallet Intelligence

Inspect transaction

wallet-intelligence_transaction
Read-onlyIdempotent

Inspect a supplied transaction hash on Base Mainnet with gas analysis and USD cost estimation. Price $0.03 USDC. POST /api/v1/wallet-intelligence/transaction. An unpaid call returns the x402 payment terms and does not run.

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": {
      "txHash": "<txHash>"
    },
    "name": "wallet-intelligence_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYestxHash, string. Required.

Output Schema

NameRequiredDescriptionDefault
foundNofound. Boolean.
txHashNotxHash. String.
receiptNoreceipt. Object.
sourcesNosources. Array.
gasAnalysisNogasAnalysis. Object.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
transactionNotransaction. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 baseline is covered. The description adds genuinely non-schema information: the $0.03 USDC price, the POST path, and — importantly — that an unpaid call returns x402 payment terms and does not execute. Return shape is left to the output schema.

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 short sentences: capability and scope first, then price/endpoint, then the payment-failure behavior. Nothing is redundant and the most decision-relevant facts are front-loaded.

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?

For a one-parameter read-only tool with an output schema, the description covers scope, cost, transport, and the unpaid-call trap. The only gap is that it does not indicate which chain-adjacent inputs are rejected or what the analysis covers in depth, which is minor given the output schema.

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% with a single required txHash parameter that already carries a format regex. The description only says the hash is 'supplied' and adds no format, encoding, or normalization detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (inspect) and resource (a supplied transaction hash) and pins the chain to Base Mainnet plus what the output covers (gas analysis, USD cost). It is clear enough to separate from siblings like wallet-intelligence_transfers, but it never explicitly contrasts itself with wallet-intelligence_analyze or the security tools.

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?

Usage context is implied by 'supplied transaction hash' and the chain scope, and the payment note tells the agent a call has a cost. However there is no explicit when-to-use vs alternatives guidance, e.g. when to reach for transaction inspection instead of analyze or transfers.

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