automaton

websearch__search

Ranked web search merged from Hacker News, GitHub, Wikipedia and Stack Exchange. 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/search

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

Input Schema

Name	Required	Description	Default
`q`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```

Changed5 schema fields changedNov 6, 2026

removedInput schema / properties / chars

Removed value: -{
-  "description": "Markdown chars per page (200-8000)",
-  "type": "integer"
-}

removedInput schema / properties / extract

Removed value: -{
-  "description": "How many hits get full text (0-5)",
-  "type": "integer"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Max results (1-25)",
-  "type": "integer"
-}

removedInput schema / properties / q / description
```
Removed value: -"Search query"
```

removedInput schema / properties / url

Removed value: -{
-  "description": "Single URL to convert to markdown instead of searching",
-  "type": "string"
-}

Changed9 schema fields changedNov 2, 2026

addedInput schema / properties / chars

Added value: +{
+  "description": "Markdown chars per page (200-8000)",
+  "type": "integer"
+}

addedInput schema / properties / extract

Added value: +{
+  "description": "How many hits get full text (0-5)",
+  "type": "integer"
+}

removedInput schema / properties / format

Removed value: -{
-  "enum": [
-    "json",
-    "md"
-  ],
-  "type": "string"
-}

addedInput schema / properties / limit / description
```
Added value: +"Max results (1-25)"
```
removedInput schema / properties / limit / maximum
```
Removed value: -20
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

removedInput schema / properties / sources

Removed value: -{
-  "description": "Comma list of hn,github,wiki,se",
-  "type": "string"
-}

addedInput schema / properties / url

Added value: +{
+  "description": "Single URL to convert to markdown instead of searching",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

Changed5 schema fields changedNov 2, 2026

removedInput schema / properties / format / description
```
Removed value: -"Response format (default json)"
```

changedInput schema / properties / format / enum

Previous value: -[
-  "json",
-  "compact"
-]New value: +[
+  "json",
+  "md"
+]

removedInput schema / properties / limit / description
```
Removed value: -"Max results (default 10)"
```
changedInput schema / properties / limit / maximum
```
Previous value: -25New value: +20
```

changedInput schema / properties / sources / description

Previous value: -"Comma list of hn,github,wiki,se (default all)"New value: +"Comma list of hn,github,wiki,se"

Changed6 schema fields changedNov 2, 2026

addedInput schema / properties / format

Added value: +{
+  "description": "Response format (default json)",
+  "enum": [
+    "json",
+    "compact"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results (default 10)",
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / properties / packages

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

addedInput schema / properties / q

Added value: +{
+  "description": "Search query",
+  "type": "string"
+}

addedInput schema / properties / sources

Added value: +{
+  "description": "Comma list of hn,github,wiki,se (default all)",
+  "type": "string"
+}

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

Changed4 schema fields changedNov 1, 2026
- removedInput schema / properties / limit
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / packages
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / q
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / sources
```
Removed value: -{
-  "type": "string"
-}
```

Changed10 schema fields changedNov 1, 2026

removedInput schema / properties / chars

Removed value: -{
-  "description": "Max markdown chars per page",
-  "maximum": 8000,
-  "minimum": 200,
-  "type": "integer"
-}

removedInput schema / properties / extract

Removed value: -{
-  "description": "Pages to extract (default 4)",
-  "maximum": 6,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / format

Removed value: -{
-  "description": "json (default) or md",
-  "enum": [
-    "json",
-    "md"
-  ],
-  "type": "string"
-}

removedInput schema / properties / limit / description
```
Removed value: -"Max results, default 10"
```
removedInput schema / properties / limit / maximum
```
Removed value: -20
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / limit / type

Previous value: -"integer"New value: +"number"

removedInput schema / properties / q / description
```
Removed value: -"Search query"
```

removedInput schema / properties / sources / description

Removed value: -"Comma list of hn,github,wiki,se (default all)"

removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / chars

Added value: +{
+  "description": "Max markdown chars per page",
+  "maximum": 8000,
+  "minimum": 200,
+  "type": "integer"
+}

addedInput schema / properties / extract

Added value: +{
+  "description": "Pages to extract (default 4)",
+  "maximum": 6,
+  "minimum": 0,
+  "type": "integer"
+}

Changed9 schema fields changedOct 31, 2026

removedInput schema / properties / extract

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

addedInput schema / properties / format

Added value: +{
+  "description": "json (default) or md",
+  "enum": [
+    "json",
+    "md"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit / description
```
Added value: +"Max results, default 10"
```
addedInput schema / properties / limit / maximum
```
Added value: +20
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / q / description
```
Added value: +"Search query"
```

addedInput schema / properties / sources

Added value: +{
+  "description": "Comma list of hn,github,wiki,se (default all)",
+  "type": "string"
+}

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

AddedOct 30, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose two genuinely important traits an agent cannot get elsewhere: the $0.01 USDC cost on Base and the x402 payment envelope location in params._meta, plus the HTTP endpoint. However, it says nothing about result format, ranking behavior, default/maximum value of limit, latency, or failure modes when payment is missing.

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?

Front-loaded with the capability, then payment mechanics, then transport. Three dense clauses with no filler. The endpoint URL is arguably redundant against the transport info but is cheap and occasionally useful.

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?

For a two-parameter, no-output-schema tool the description covers purpose and payment adequately, which is the hardest part. It is incomplete on the input side (query and limit semantics) and on what a caller receives back, which an agent needs before spending $0.01 per 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%, so the description must compensate and does not: neither 'q' (query string syntax, operators) nor 'limit' (default, range, cost impact) is explained. The one useful addition is documenting an out-of-schema payment parameter, params._meta["x402/payment"], which is real value but leaves both declared parameters opaque.

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 specific verb+resource ('Ranked web search') and names the four merged corpora (Hacker News, GitHub, Wikipedia, Stack Exchange), which meaningfully separates it from siblings like websearch__brief, websearch__dossier and websearch__searchbatch. It stops short of explicitly naming which sibling to prefer, so it is clear but not fully differentiated.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the many nearby alternatives (websearch__brief, websearch__dossier, websearch__searchbatch, websearch__quotes). The agent must infer from the word 'search' that this is the plain ranked-search entry point.

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?