Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

chainread__payment

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

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

Input Schema

NameRequiredDescriptionDefault
opsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
-}
  2. Changed3 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / hash
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / to
      Added value: +{
+  "type": "string"
+}
  3. Added

TDQS

C2.6/5.0
Behavior3/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 disclose meaningful behavior: read-only nature, the x402 payment requirement, price, network, and the HTTP endpoint. It omits what happens on payment failure, whether payment is per-call or per-op, and how the 'ops' batch is executed, leaving significant behavioral gaps for a paid mutation-adjacent tool.

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 cramming nine capabilities plus pricing and transport details. The critical payment prerequisite is buried at the end rather than front-loaded, and the capability list is redundant with sibling tools, so much of the text does not earn its place.

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?

For a tool with a nested, fully undocumented parameter and no output schema, the description should explain the ops structure and return shape. Instead it lists capabilities and pricing but leaves the actual invocation contract (op values, address semantics, response format) unexplained.

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?

There is one parameter ('ops'), a nested array of objects with 'op' and 'address' fields at 0% schema description coverage. The description hints at batching ('20 reads in one call') but never explains the 'op' vocabulary, valid values, or how 'address' is used, so it does not compensate for the undocumented schema.

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

Purpose3/5

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

The description names a specific domain (read-only Base/Ethereum chain data) and enumerates concrete capabilities (ENS, ERC-20 logs, multiread, preflight, verdict, balances, gas, tx lookup, watchlist). However, the tool name 'payment' does not match the described function, and the sprawling capability list overlaps almost entirely with dedicated siblings (chainread__balance, chainread__ens, chainread__erc20_transfers, chainread__multiread, chainread__preflight, chainread__verdict, chainread__gas, chainread__tx, chainread__watch), with no differentiation of what this tool uniquely does.

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?

The description states a payment prerequisite ($0.01 USDC on Base via x402 in params._meta) but gives no guidance on when to use this tool versus the many dedicated chainread siblings that cover the same operations. An agent cannot infer whether this is a unified gateway, a fallback, or a distinct paid endpoint.

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

All automaton toolsInspect
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