Skip to main content
Glama

txpreflight__preflight

Preflight any Base transaction before you sign: does it revert, and what will it cost in gas. GET ?to=0x..&data=0x..&value=..&urgency=normal, or POST JSON. Also vets x402 sellers. $0.01 USDC per call on Base. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/txpreflight/preflight

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": {
      "to": "<to>"
    },
    "name": "txpreflight__preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination 0x address (required).
dataNoCalldata hex, 0x-prefixed (optional).
fromNoSender 0x address (optional).
valueNoETH value in wei (optional).
urgencyNoGas urgency (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / data / description
      Added value: +"Calldata hex, 0x-prefixed (optional)."
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Sender 0x address (optional).",
      +  "type": "string"
      +}
    • addedInput schema / properties / to / description
      Added value: +"Destination 0x address (required)."
    • addedInput schema / properties / urgency / description
      Added value: +"Gas urgency (optional)."
    • addedInput schema / properties / urgency / enum
      Added value: +[
      +  "slow",
      +  "normal",
      +  "fast"
      +]
    • addedInput schema / properties / value / description
      Added value: +"ETH value in wei (optional)."
    • addedInput schema / required
      Added value: +[
      +  "to"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / tx
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / urgency
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "type": "string"
      +}
  3. Changed7 schema fields changed
    • removedInput schema / properties / data
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / from
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / owner
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / spender
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / to
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / token
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / tx
      Added value: +{
      +  "type": "string"
      +}
  4. Changed3 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / from
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "type": "string"
      +}
  5. Changed8 schema fields changed
    • removedInput schema / properties / amount_usd
      Removed value: -{
      -  "description": "/verify: minimum USD that must have transferred",
      -  "type": "number"
      -}
    • removedInput schema / properties / asset
      Removed value: -{
      -  "description": "/verify: ERC-20 to check (default USDC on Base)",
      -  "type": "string"
      -}
    • addedInput schema / properties / owner
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / pay_from
      Removed value: -{
      -  "description": "/verify: require this sender",
      -  "type": "string"
      -}
    • removedInput schema / properties / pay_to
      Removed value: -{
      -  "description": "/verify: require this recipient",
      -  "type": "string"
      -}
    • addedInput schema / properties / spender
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / token
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / tx
      Removed value: -{
      -  "description": "Transaction hash, 0x + 64 hex",
      -  "type": "string"
      -}
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the paid model ($0.01 USDC per call on Base, eip155:8453), the exact x402 payment location (params._meta["x402/payment"]), and the transport (GET query string or POST JSON, with the endpoint URL). It does not state whether the call is non-destructive/read-only or what happens on payment failure, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the GET/POST and endpoint details are useful, but the pricing is stated twice in near-identical sentences ("$0.01 USDC per call on Base. Price: $0.01 per call in USDC on Base (eip155:8453)"), which wastes space in a definition that is otherwise compact.

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 5-parameter tool with no annotations and no output schema, the description supplies the missing pieces an agent needs before calling: what the result answers (revert status and gas cost), how to invoke it over HTTP, and the payment precondition. Only the read-only/non-signing nature and failure behavior on unpaid calls remain unstated.

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%, so the schema already documents all five parameters with types and enums; the baseline is 3. The description echoes four of them in query-string form (to, data, value, urgency) but omits `from` and adds no format or semantic detail beyond the schema.

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?

States a specific verb and resource: preflight a Base transaction before signing, answering two concrete questions (will it revert, what will gas cost). The secondary clause "also vets x402 sellers" muddies the single purpose and is not reconciled with the primary use case, and no sibling (e.g. chainread__preflight, x402_preflight__check) is named for differentiation.

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?

"Before you sign" implies the usage moment clearly enough for an agent building a transaction flow, but there are no explicit exclusions and no guidance on when to use the x402-seller-vetting mode versus the transaction mode. No alternative tool is named, so selection against the many sibling preflight/allowance/guard tools is left to inference.

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