automaton

web_extract__dossier

Structured multi-signal dossier for one page: text, metadata, headings and links together. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/web-extract/dossier

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "web_extract__dossier"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026
- removedInput schema / properties / format
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / url / format
```
Added value: +"uri"
```
- addedInput schema / required
```
Added value: +[
+  "url"
+]
```
Changed4 schema fields changedNov 6, 2026
- removedInput schema / properties / format / description
```
Removed value: -"Body text format (default text)"
```
- removedInput schema / properties / format / enum
```
Removed value: -[
-  "text",
-  "markdown"
-]
```
- removedInput schema / properties / url / description
```
Removed value: -"Public http(s) URL of the page to profile"
```
- removedInput schema / required
```
Removed value: -[
-  "url"
-]
```
AddedNov 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does deliver key operational facts: the call costs $0.01 in USDC on Base (eip155:8453), payment is passed via params._meta["x402/payment"], and the transport is POST to a specific endpoint. It does not cover failure behavior when payment is missing, rate limits, or response size limits.

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 sentences, both front-loaded: the capability first, then the commercial and transport mechanics. Nothing is repeated and nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter paid tool with no annotations and no output schema, the description covers what is returned, what it costs, how to pay, and where to send the request. The remaining gap is error and limit behavior, which matters here because a failed payment path can block the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'url' parameter, so the description must compensate; 'for one page' establishes what the URL targets. More importantly, it discloses a payment parameter that does not appear in the input schema at all, which the agent cannot learn from structured fields.

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 names a specific resource and enumerates its contents: a 'structured multi-signal dossier for one page: text, metadata, headings and links together.' That is enough for an agent to distinguish it from the lighter extracts in the web_extract family, though it never names those siblings explicitly.

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: 'one page' and 'together' suggest it is the all-in-one option when several page signals are needed at once. There is no explicit when-to-use or when-not-to-use statement, and no reference to alternatives such as the single-signal extract or chunk tools.

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?