Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

transfer_preflight

Read-onlyIdempotent

chainpeek: Preflight a USDC or USDT transfer: balance, gas, nonce, blacklist, recipient, simulation. For OFAC screening use check_sanctions; for a wallet's past pulls use check_wallet_drain. Returns a verdict (pass, warn or fail) for one planned ERC-20 transfer, with a row per check in checks (token balance, gas balance, pending nonce, issuer blacklist for sender and recipient, paused, recipient sanity, address-poisoning lookalike, simulated transfer(to, amount) with its revert reason, decimals and raw amount) and the non-passing ones in reasons. Read-only: nothing is signed or sent. A part that cannot be read is not_checked with a reason (verdict warn); a token without the blacklist function is not_available, not a fail. Lookalike check on Ethereum and Base only. Bad input is a 422 (not charged). Typically 1-4 s. Price: USD 0.01. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/gas-price-api.html

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>",
      "token": "<token>",
      "from": "<from>",
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "transfer_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe recipient (0x + 40 hex).
fromYesThe sending wallet (0x + 40 hex).
chainYesethereum, base, polygon, bnb or arbitrum.
tokenYesUSDC, USDT (the chain's native issuer contract) or an ERC-20 contract address.
amountYesAmount in token units as a positive decimal string, e.g. "250.5" (not raw units).

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
noteNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
tokenNo
amountNo
checksNo
limitsNo
reasonsNo
verdictNo
budget_sNo
read_onlyNo
amount_rawNo
elapsed_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / amount / title
      Removed value: -"Amount"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / from / title
      Removed value: -"From"
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / properties / token / title
      Removed value: -"Token"
    • removedInput schema / title
      Removed value: -"transfer_preflightArguments"
    • removedOutput schema / properties / checks / items
      Removed value: -{
      -  "properties": {
      -    "amount": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "amount_raw": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "balance": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "balance_raw": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "code": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "decimals": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "estimated_fee": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "gas_price_gwei": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "gas_units": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "id": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "message": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "native_balance": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "native_symbol": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "nonce_latest": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "nonce_pending": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "recipient_type": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "revert_reason": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "revert_selector": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "risk": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "status": {
      -      "enum": [
      -        "pass",
      -        "warn",
      -        "fail",
      -        "not_checked",
      -        null
      -      ],
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / limits / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / reasons / items
      Removed value: -{
      -  "properties": {
      -    "check": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "message": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "status": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / token / properties
      Removed value: -{
      -  "address": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "decimals": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "symbol": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description goes further: nothing is signed or sent, unreadable parts become `not_checked` with verdict `warn`, a token lacking the blacklist function returns `not_available` rather than failing, and bad input is a 422 that is not charged. The only gap is minor inconsistency in that the text frames the tool as USDC/USDT while the schema also accepts arbitrary ERC-20 contract addresses.

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?

Purpose and alternatives are front-loaded in the first sentence, and no sentence is pure filler, but the remainder is a single dense block mixing return-shape, failure-mode, chain-coverage, latency and pricing facts. It is efficient rather than well-structured.

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?

An output schema exists, yet the description still names the top-level fields (`verdict`, `checks`, `reasons`) and the specific sub-checks, plus the edge-case verdicts. For a five-parameter read-only preflight tool, nothing an agent needs to call it or interpret the result is missing.

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 description coverage is 100%, so the schema already defines every parameter including the amount format and token pattern. The description adds only scattered meaning (that `amount` is interpreted in token units and that the response reports decimals and raw amount), which is a modest increment over the structured fields.

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?

States a specific verb and resource ('Preflight a USDC or USDT transfer') and enumerates exactly which checks run: balance, gas, nonce, blacklist, recipient, simulation. It explicitly routes two adjacent needs to named siblings (check_sanctions for OFAC, check_wallet_drain for past pulls), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use-one-instead conditions by naming two alternatives and the question each answers. It also supplies operational context an agent needs before calling: read-only, typical 1-4 s latency, USD 0.01 price, and 10 free chain reads per IP per UTC day.

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.