automaton

websearch__answer

Question -> cited extractive answer. 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/answer

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

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"
-}
```
Changed4 schema fields changedNov 12, 2026
- addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / properties / q
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / reset
```
Removed value: -{
-  "type": "boolean"
-}
```
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

Changed8 schema fields changedNov 12, 2026

removedInput schema / properties / chars

Removed value: -{
-  "description": "Chars per page, default 2500",
-  "maximum": 8000,
-  "minimum": 500,
-  "type": "integer"
-}

removedInput schema / properties / extract

Removed value: -{
-  "description": "Pages to extract, default 3",
-  "maximum": 8,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / format

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

removedInput schema / properties / limit

Removed value: -{
-  "description": "Search results to consider, default 6",
-  "maximum": 10,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / q / description
```
Removed value: -"The question"
```
addedInput schema / properties / reset
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / properties / sources

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

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

AddedNov 11, 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 the full burden, and it does disclose the most consequential behavior: a $0.01 USDC charge on Base via x402 in params._meta["x402/payment"]. That is genuinely useful non-structured context. It still omits what happens on an unpaid request (presumably a 402 challenge), any rate limits, and how much source material the extractive answer draws on.

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 input-to-output contract, then payment terms, then the HTTP endpoint — three tight fragments with no filler. The endpoint URL is arguably redundant for an MCP caller 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 one-parameter tool with no output schema, it covers the essentials: what goes in, the shape of the answer, and the payment mechanics. What it lacks is the payment failure path and any description of the citation structure returned, which matters because no output schema exists to describe it.

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% and the single parameter q is undocumented, but the description's "Question ->" framing tells the agent what q should contain. It also reveals that an additional _meta["x402/payment"] field must be supplied even though that field is absent from the input schema, which is meaning the schema cannot provide. It does not specify question length, language, or formatting.

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?

"Question -> cited extractive answer" names both the input and the distinctive output format (extractive, with citations), which is more specific than a bare "search" label. It does not differentiate itself from siblings such as websearch__search or websearch__brief, leaving the agent to guess which produces plain results versus a synthesized brief.

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 statement and no mention of alternatives despite several close siblings (search, brief, dossier, topicwatch). The arrow notation implies Q&A rather than listing, but the choice between this and websearch__search is left entirely to inference.

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?