automaton

websearch__topicwatch

Only what is NEW since your last poll of the same query. 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/websearch/topicwatch

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

Input Schema

Name	Required	Description	Default
`q`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026
- removedInput schema / properties / limit
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / q
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / url
```
Removed value: -{
-  "type": "string"
-}
```

Changed5 schema fields changedNov 12, 2026

addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```

removedInput schema / properties / q

Removed value: -{
-  "description": "Search query to monitor",
-  "type": "string"
-}

removedInput schema / properties / reset

Removed value: -{
-  "description": "Rebuild the baseline instead of diffing",
-  "type": "boolean"
-}

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

AddedNov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it usefully discloses the payment model: $0.01 per call in USDC on Base (eip155:8453) via x402 in params._meta["x402/payment"], plus the raw HTTP endpoint. What it omits is equally important: the behavior on a first poll with no prior state, and whether state is keyed per-query on the caller. Payments and auth are covered; stateful edge cases are not.

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

Conciseness5/5

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

Two short sentences with the differentiating behavior front-loaded, followed by the cost and transport details an agent needs before calling. No padding or restatement of the tool name.

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?

With no output schema and no annotations, the description should describe the return shape and first-poll behavior. It covers payment and transport thoroughly but leaves the response format and the no-prior-state case undefined, which matters for a stateful delta tool.

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 (q) with 0% schema description coverage, so the description must compensate. It does convey the key semantic: q is the query that state is keyed on and must be repeated verbatim for the delta to work. It adds nothing about query syntax, length limits, or how q is normalized for state matching, so the compensation is partial.

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 states a specific behavior: it returns only results that are NEW since the previous poll of the same query. That delta semantics is what distinguishes it from a plain search or feed tool. However, it never names a sibling (e.g. websearch__search or websearch__feed) as the non-delta alternative, so the differentiation is left implicit.

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?

"since your last poll of the same query" implies a recurring polling pattern and that the query string must stay stable across calls, which is useful usage guidance. But it does not say when to choose this over websearch__search or websearch__watch, or what state means for a query you have never polled.

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?