automaton

chainread__watch

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

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

Input Schema

Name	Required	Description	Default
`ops`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

removedInput schema / properties / addresses

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / chain

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

addedInput schema / properties / ops

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

AddedNov 3, 2026

TDQS

A3.9/5.0

Behavior5/5

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

With zero annotations, the description provides crucial operational behavior, detailing that it is read-only, specifies the network (Base), and outlines the pricing and payment mechanism (x402), which is vital behavioral context.

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 definition is a massive, dense run-on sentence listing dozens of features. This structure sacrifices readability and front-loading of the most critical information for maximal content packing.

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?

Given the complexity of the stated features and the lack of any structural metadata (like annotations or output schemas), the description provides maximum possible contextual completeness, including operational logistics like network and pricing.

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%, meaning the description is the only source of truth for the inputs. However, it doesn't specify the valid values for 'op' or how 'address' should be formatted, making the parameters poorly supported.

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?

The description clearly identifies the tool's domain (Base/Ethereum chain data) and enumerates a comprehensive set of functionalities, including specific read types like ENS resolution, ERC-20 logs, and tx preflight.

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?

It strongly implies usage for monitoring and data retrieval but lacks explicit guidance on when to choose this tool over related siblings (e.g., chainread__verdict or chainread__txlookup).

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?