Skip to main content
Glama

Tx batch status

tx_batch_status
Read-onlyIdempotent

Check status, confirmations, gas and fee for up to 8 transactions across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood). $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "txs": "<txs>"
    },
    "name": "tx_batch_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
txsYesup to 8 comma-separated chain:0xhash items, e.g. base:0x..., arbitrum:0x...
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / txs / description
      Previous value: -"up to 8 comma-separated chain:0xhash items, e.g. base:0x..."New value: +"up to 8 comma-separated chain:0xhash items, e.g. base:0x..., arbitrum:0x..."
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds genuinely useful non-schema behavior: a $0.003 per-call price, the x402 payment handshake, and accepted payment assets (USDC on Arc/Base/Solana, XNT on X1). It does not state what happens when a hash is unknown, whether the first unpaid call returns anything except terms, or any rate limits, so it stays a solid 3 rather than higher.

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?

Three sentences, purpose front-loaded, zero filler. The pricing and payment detail is dense but every clause carries operational weight; the only mild weakness is that commerce mechanics are packed into the same breath as the capability statement, making the sentence slightly overloaded.

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?

There is no output schema, so the description must carry the return surface — and it does by naming status, confirmations, gas and fee. The two-step payment requirement, which is the main way an agent could call this incorrectly, is fully spelled out. Not covered: partial results when some of the 8 hashes are invalid, and the minor inconsistency of calling these '8 EVM chains' while listing Arc, Robinhood and X1.

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 description coverage is 100%, so the baseline is 3 and the bar is to add meaning beyond the schema. The description does: it explains that `payment` is the second half of a two-call flow ('call once without `payment` for the terms... call again with `payment`'), which clarifies why the parameter is optional. The `txs` format is not elaborated beyond the schema's own example, keeping it below a 5.

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 ('Check') with the exact resources returned (status, confirmations, gas and fee) plus an explicit scope cap ('up to 8 transactions across 8 EVM chains') and enumerates the chains. An agent can distinguish this from the single-transaction sibling evm_tx without opening either schema.

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 a clear operating procedure: call once without `payment` to get terms, sign them, call again with `payment`. What is missing is explicit routing guidance – it never says to use evm_tx (or similar) for a single transaction, so the batch-vs-single choice is only implied by 'up to 8'.

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