Skip to main content
Glama

txpreflight__verify

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/verify

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__verify"
  }
}

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
      Added value: +{
      +  "description": "Calldata hex, 0x-prefixed (optional).",
      +  "type": "string"
      +}
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Sender 0x address (optional).",
      +  "type": "string"
      +}
    • removedInput schema / properties / hash
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Destination 0x address (required).",
      +  "type": "string"
      +}
    • addedInput schema / properties / urgency
      Added value: +{
      +  "description": "Gas urgency (optional).",
      +  "enum": [
      +    "slow",
      +    "normal",
      +    "fast"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "description": "ETH value in wei (optional).",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "to"
      +]
  2. Changed4 schema fields changed
    • removedInput schema / properties / amount_usd
      Removed value: -{
      -  "type": "number"
      -}
    • addedInput schema / properties / hash
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / pay_to
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / tx
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed9 schema fields changed
    • addedInput schema / properties / amount_usd
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / data
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / from
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / owner
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / pay_to
      Added 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.5/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 that each call costs $0.01 in USDC on Base (eip155:8453), that payment must be supplied via x402 in params._meta["x402/payment"], and it gives the concrete HTTP endpoint and accepted methods. It still omits failure modes, rate limits, or what a revert/gas response actually contains.

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 core purpose is front-loaded and the transport detail is useful, but the pricing is stated twice ("$0.01 USDC per call on Base" and again as "Price: $0.01 per call in USDC on Base") and the payment mechanism is restated as well. Roughly a quarter of the text is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, unannotated, no-output-schema tool this covers payment, transport, and the rough shape of the answer, which is the minimum an agent needs to call it. It does not describe the response structure beyond "revert / gas cost", nor whether the result is a simulation receipt, a boolean, or an error payload.

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 every parameter is already documented and the baseline is 3. The description adds modest value by showing the GET query-string form (to/data/value/urgency) versus POST JSON, but says nothing about defaults, the urgency enum's effect, or units beyond what the schema states.

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?

"Preflight any Base transaction before you sign: does it revert, and what will it cost in gas" gives a specific verb, a specific resource (Base transaction), and the two outputs an agent cares about. The trailing "Also vets x402 sellers" widens the scope without explaining how, and there is no differentiation from sibling preflight tools (txpreflight__preflight, chainread__txpreflight, pageaudit__txpreflight).

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 correct moment to call it, which is a real usage cue. However, there is no statement of when not to use it, no prerequisites, and no reference to which sibling to pick for related checks, so selection among the several preflight 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