automaton

chgwatch__watchlist

Poll every URL in your watchlist in one call and get per-URL changed flags. 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/chgwatch/watchlist

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": "chgwatch__watchlist"
  }
}

Input Schema

Name	Required	Description	Default
`action`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- removedInput schema / properties / urls
```
Removed value: -{
-  "type": "string"
-}
```

Changed6 schema fields changedNov 2, 2026

addedInput schema / properties / action
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / mode

Removed value: -{
-  "description": "What to compare",
-  "enum": [
-    "text",
-    "markdown",
-    "meta",
-    "links"
-  ],
-  "type": "string"
-}

removedInput schema / properties / store

Removed value: -{
-  "description": "true to save this snapshot as the new baseline",
-  "type": "string"
-}

removedInput schema / properties / url

Removed value: -{
-  "description": "URL to diff against its stored baseline",
-  "type": "string"
-}

addedInput schema / properties / urls
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / required
```
Removed value: -[
-  "url"
-]
```

Changed7 schema fields changedOct 31, 2026

removedInput schema / description

Removed value: -"Use watchlist=1 to poll your saved list, or urls=a,b,c for a batch check. Your watchlist is stored server-side under your payer wallet, so you never resend URLs."

addedInput schema / properties / mode

Added value: +{
+  "description": "What to compare",
+  "enum": [
+    "text",
+    "markdown",
+    "meta",
+    "links"
+  ],
+  "type": "string"
+}

addedInput schema / properties / store

Added value: +{
+  "description": "true to save this snapshot as the new baseline",
+  "type": "string"
+}

addedInput schema / properties / url

Added value: +{
+  "description": "URL to diff against its stored baseline",
+  "type": "string"
+}

removedInput schema / properties / urls

Removed value: -{
-  "description": "Comma-separated URLs to batch-check (up to 20). Omit when watchlist=1.",
-  "type": "string"
-}

removedInput schema / properties / watchlist

Removed value: -{
-  "description": "Set to 1 to check every URL in your saved watchlist (keyed to your paying wallet).",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "url"
+]
```

Changed3 schema fields changedOct 31, 2026

addedInput schema / description

Added value: +"Use watchlist=1 to poll your saved list, or urls=a,b,c for a batch check. Your watchlist is stored server-side under your payer wallet, so you never resend URLs."

addedInput schema / properties / urls

Added value: +{
+  "description": "Comma-separated URLs to batch-check (up to 20). Omit when watchlist=1.",
+  "type": "string"
+}

addedInput schema / properties / watchlist / description

Added value: +"Set to 1 to check every URL in your saved watchlist (keyed to your paying wallet)."

AddedOct 31, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose the cost ($0.01/call in USDC on Base, eip155:8453), the x402 payment mechanism and its parameter location, and the underlying HTTP endpoint. What is missing is failure behavior: what happens with an empty watchlist, polling frequency assumptions, or rate limits.

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 tight sentences: purpose first, then pricing, then transport. Every sentence carries distinct information, with no filler or repetition of the title.

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?

For a one-parameter polling tool with no output schema and no annotations, the description covers purpose, return shape ('per-URL changed flags'), payment and cost, and the endpoint. The one real gap, the 'action' parameter, is the only thing an agent would still have to guess at.

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 a single opaque 'action' parameter, so the description must compensate, and it does not. It documents the x402 payment payload but never explains a valid 'action' value or whether it is required, leaving the only input entirely unexplained.

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?

The description opens with a specific verb and resource: 'Poll every URL in your watchlist in one call and get per-URL changed flags.' That makes the batch-checking scope clear. It does not name the sibling tools (chgwatch__diff, chgwatch__diffmulti, chgwatch__watch), so an agent must infer how it differs from those.

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 implied rather than stated: you call it when you want a changed flag for every watchlist URL at once. There is no explicit when-not guidance, no prerequisites (such as a non-empty watchlist), and no named alternative.

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?