automaton

x402index__demandreport_md

Vet x402 sellers before you pay: live 402 charge decode, fairness vs a 59k-listing index, and a one-call full-catalog audit. New: /pick finds the right paid endpoint for a task. 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/x402index/demandreport.md

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

Input Schema

Name	Required	Description	Default
`task`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026
- removedInput schema / properties / base
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / task
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / base
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / resource
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 6, 2026
- removedInput schema / properties / days
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / resource
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 3, 2026
RemovedNov 2, 2026

Changed4 schema fields changedNov 2, 2026

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

addedInput schema / properties / resources

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / urls

Removed value: -{
-  "description": "Comma-separated https x402 endpoints to vet (up to 20). POST body may instead be {\"urls\": [...]}",
-  "type": "string"
-}

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

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / urls

Added value: +{
+  "description": "Comma-separated https x402 endpoints to vet (up to 20). POST body may instead be {\"urls\": [...]}",
+  "type": "string"
+}

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

Changed4 schema fields changedNov 2, 2026

removedInput schema / properties / resource

Removed value: -{
-  "description": "The x402 endpoint URL to investigate",
-  "type": "string"
-}

removedInput schema / properties / resources

Removed value: -{
-  "description": "Batch: up to 25 endpoint URLs in one call",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / url

Removed value: -{
-  "description": "Alias for resource",
-  "type": "string"
-}

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

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / resources

Added value: +{
+  "description": "Batch: up to 25 endpoint URLs in one call",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 31, 2026

addedInput schema / properties / resource / description

Added value: +"The x402 endpoint URL to investigate"

addedInput schema / properties / url

Added value: +{
+  "description": "Alias for resource",
+  "type": "string"
+}

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

AddedOct 30, 2026

TDQS

C2.9/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavioral facts an agent needs — price ($0.01 USDC on Base eip155:8453), the payment envelope (params._meta['x402/payment']), and the HTTP transport — which is more than most. But it never says what the 'demand report' actually contains, whether the call fails without payment, or what happens on an unpaid request, leaving the core output behavior opaque.

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?

The core capability is front-loaded in the first clause, and the pricing/transport details are packed into a compact second half. It reads as marketing copy rather than specification, and the 'New: /pick...' insert is off-topic for this tool, but it is short with no filler sentences.

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

Completeness2/5

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

With no output schema, no annotations, and two parameters at 0% schema coverage, the description needed to explain return shape and parameter meaning. Instead it gives a sales pitch plus payment mechanics, so an agent knows how to pay but not what it will get back or how to set `task` and `limit`.

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% for both `task` and `limit`, so the description must compensate and does not. The word 'task' appears only in the context of the /pick sibling, and `limit` is never addressed at all, leaving both parameters semantically undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Vet x402 sellers') and a broad resource area (charge decode, fairness vs a 59k-listing index, full-catalog audit), but never says plainly what this tool returns or how it differs from siblings like x402index__audit, x402index__verdict, or x402check__report. It also mixes in a pitch for /pick (a separate sibling, x402index__pick), muddying rather than sharpening the purpose.

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?

'before you pay' implies the usage moment, and mentioning /pick hints at an alternative for endpoint selection, but there are no explicit when-to-use/when-not-to-use statements or named alternatives among the many x402 vetting siblings. Usage is inferable rather than stated.

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?