automaton

websearch__dossier

Multi-source research dossier: search, extract pages, headings, word counts, deduped digest. 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/dossier

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

Input Schema

Name	Required	Description	Default
`q`	No

Schema Changelog

Changes observed during successful MCP inspections.

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 / description
```
Added value: +"Markdown chars per page (200-8000)"
```
- addedInput schema / properties / extract / description
```
Added value: +"How many hits get full text (0-5)"
```
- removedInput schema / properties / extract / maximum
```
Removed value: -6
```
- removedInput schema / properties / extract / minimum
```
Removed value: -1
```
- addedInput schema / properties / limit / description
```
Added value: +"Max results (1-25)"
```
- addedInput schema / properties / q / description
```
Added value: +"Search query"
```
- removedInput schema / properties / sources
```
Removed value: -{
-  "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"
-]
```
Changed9 schema fields changedNov 2, 2026
- removedInput schema / properties / chars / description
```
Removed value: -"Max characters per source (default 2000)"
```
- removedInput schema / properties / chars / maximum
```
Removed value: -20000
```
- removedInput schema / properties / chars / minimum
```
Removed value: -200
```
- removedInput schema / properties / extract / description
```
Removed value: -"How many sources to extract (default 4)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Results to search (default 10)"
```
- removedInput schema / properties / limit / maximum
```
Removed value: -25
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / q / description
```
Removed value: -"Research query"
```
- addedInput schema / properties / sources
```
Added value: +{
+  "type": "string"
+}
```

Changed6 schema fields changedNov 2, 2026

addedInput schema / properties / chars

Added value: +{
+  "description": "Max characters per source (default 2000)",
+  "maximum": 20000,
+  "minimum": 200,
+  "type": "integer"
+}

addedInput schema / properties / extract

Added value: +{
+  "description": "How many sources to extract (default 4)",
+  "maximum": 6,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Results to search (default 10)",
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / properties / packages

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

addedInput schema / properties / q

Added value: +{
+  "description": "Research query",
+  "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"
-]
```

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries real behavioral weight and delivers on the expensive-to-discover parts: cost ($0.01/call in USDC on Base), the x402 payment channel in params._meta, and the concrete HTTP endpoint. It omits rate limits, failure/refund behavior, and what the returned digest looks like.

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?

One dense but front-loaded sentence plus a payment clause and endpoint; nothing is redundant. Payment details are somewhat technical but do earn their place for a paid tool.

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 one-parameter paid research tool with no output schema, the definition covers purpose, cost, payment mechanism, and endpoint. It leaves the agent guessing about output shape, query semantics, and how it differs from the many sibling search/brief/dossier tools.

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?

Schema coverage is 0% for the single parameter 'q', but the description's 'search' wording makes it inferable that q is the research query. Beyond that it adds no syntax, query-format, or length guidance for q, so it does not fully compensate for the undocumented schema.

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: 'Multi-source research dossier: search, extract pages, headings, word counts, deduped digest.' That distinguishes it in kind from a plain search, but it never names its closest siblings (websearch__search, websearch__brief, web_extract__dossier) so the agent must infer the boundary.

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 explicit when-to-use or when-not guidance and no mention of alternatives, despite many overlapping siblings in the websearch/web_extract/x402index families. The phrase 'multi-source research dossier' only weakly implies a comprehensive-research use case.

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?