automaton

chainread__txpreflight

Read-only Base/Ethereum chain data for AI agents: ENS name and reverse resolution, recent ERC-20 transfer logs, batched multi-read (20 reads in one call), tx preflight, token safety verdict, balances, gas, tx lookup, and a stateful watchlist monitor. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/chainread/txpreflight

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chainread__txpreflight"
  }
}

Input Schema

Name	Required	Description	Default
`ops`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 6, 2026

removedInput schema / properties / chain

Removed value: -{
-  "type": "string"
-}

removedInput schema / properties / data

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / ops

Added value: +{
+  "items": {
+    "properties": {
+      "address": {
+        "type": "string"
+      },
+      "op": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / to

Removed value: -{
-  "type": "string"
-}

AddedNov 3, 2026

TDQS

C2.2/5.0

Behavior3/5

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

With no annotations, the description does carry useful operational context: it is read-only, costs $0.01 per call in USDC on Base, requires x402 payment in params._meta, and gives the HTTP endpoint. However, it never explains what a preflight actually does behaviorally (simulation? revert prediction? gas estimate?) or what the response contains.

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

Conciseness2/5

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

The description is a single run-on sentence enumerating the whole service's feature set rather than front-loading this tool's purpose. Most of the text is irrelevant to invoking txpreflight.

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

Completeness2/5

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

With no annotations, no output schema, and an undocumented nested parameter, the description should explain what preflight checks and how to populate ops. Instead it only supplies pricing and transport details, leaving the core invocation semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'ops' array of {op, address} objects, and the description does not explain the 'op' values, the address semantics, or the batching limit for this tool. The passing mention of 'batched multi-read (20 reads in one call)' is about a different capability and does not clarify ops.

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

Purpose2/5

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

The description is a service-level catalog listing many capabilities (ENS, ERC-20 logs, multiread, balances, gas, tx lookup, watchlist) with 'tx preflight' buried as one item. It never states what this specific tool does as a verb+resource, and it does not distinguish it from siblings like chainread__preflight, chainread__simulate, or txpreflight__preflight.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as chainread__preflight or chainread__simulate. The agent must infer the tool's role from a generic capability list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?