automaton

basedue__watch

Create or check a watch on a Base token: returns new pools and changes since the previous call. 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/basedue/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": "basedue__watch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No
`token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedInput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedNov 6, 2026
- removedInput schema / properties / id
```
Removed value: -{
-  "type": "string"
-}
```
AddedNov 2, 2026

TDQS

B3.4/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 well: it discloses the price ($0.01 USDC on eip155:8453), the exact payment mechanism (x402 in params._meta["x402/payment"]), and the HTTP verb/endpoint. It also reveals the stateful delta semantics. It stops short of explaining what happens on first call (no prior baseline) or any error/payment-failure behavior.

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?

Two tightly packed sentences: purpose and return semantics are front-loaded, with payment and transport details following. Nearly every clause earns its place, though the create-or-check ambiguity costs a little clarity.

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?

Payment, transport, and delta behavior are covered, which is rare and valuable. But with no annotations, no output schema, and two undocumented parameters, an agent still lacks enough to know which field to supply on a first call versus a repeat call.

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 description coverage is 0% for two parameters (id, token), so the description must compensate and largely does not. The agent can infer that token starts a watch and id resumes one, but that mapping is never stated, and neither field's format or precedence is explained.

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?

States a concrete verb and resource ("Create or check a watch on a Base token") and what it returns (new pools and changes since the previous call). It is distinguishable from basedue__newpools, though the dual create/check mode is not resolved in the sentence itself.

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?

Usage is only implied: "changes since the previous call" tells the agent this is a polling/delta tool, but there is no explicit when-to-use or when-not-to-use guidance. It does not point to basedue__check, basedue__newpools, or basedue__due_alerts as alternatives for one-shot versus stateful inspection.

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?