automaton

x402index__history

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/history

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

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"
-}
```
Changed1 schema field changedNov 6, 2026
- removedInput schema / properties / days
```
Removed value: -{
-  "type": "number"
-}
```
Changed4 schema fields changedNov 3, 2026
- removedInput schema / properties / budget_usd
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / days
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / resource
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / url
```
Removed value: -{
-  "type": "string"
-}
```
Changed4 schema fields changedNov 3, 2026
- addedInput schema / properties / budget_usd
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / properties / days
```
Removed value: -{
-  "type": "number"
-}
```
- removedInput schema / properties / resource
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / resource
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / resources

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

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"
-]
```

Changed3 schema fields changedNov 2, 2026

removedInput schema / properties / resource

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

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"
+]
```

Changed3 schema fields changedNov 2, 2026

removedInput schema / properties / resource / description

Removed value: -"The x402 endpoint URL whose history you want. Alias: url."

removedInput schema / properties / url

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

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

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / resource / description

Previous value: -"The x402 endpoint URL to investigate"New value: +"The x402 endpoint URL whose history you want. Alias: url."

removedInput schema / properties / resources

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

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

AddedOct 31, 2026

TDQS

C2.1/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 genuinely useful behavior: cost ($0.01 USDC on Base, eip155:8453), the x402 payment injection point, HTTP method and endpoint URL. However, it says nothing about result shape, pagination, or failure modes, and the payment location it cites (params._meta['x402/payment']) is not present in the declared input schema, which will confuse payment construction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense marketing block whose lead sentence describes functionality other tools own, and it spends words on a 'New: /pick...' promotion irrelevant to invoking history. The only actionable facts (price, payment path, HTTP GET URL) are buried at the end.

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?

For a two-parameter, no-output-schema tool, the description should at minimum say what a history result contains and what 'task'/'limit' control. It conveys the payment/auth requirement, which is necessary, but leaves the actual return semantics and parameter behavior entirely unspecified.

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

Parameters1/5

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

Schema description coverage is 0% and there are two parameters, 'task' and 'limit', neither of which the description explains at all — no meaning, format, units, or defaults. Worse, the only parameter-like detail offered references params._meta['x402/payment'], a field that does not exist in the schema. The description fails to compensate for a total schema documentation gap.

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

Purpose2/5

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

The description never states what a 'history' call returns; it pitches the whole x402index service (charge decode, fairness vs a 59k-listing index, full-catalog audit, /pick). Those capabilities map to sibling tools (x402index__audit, x402index__verdict, x402index__pick), so an agent cannot tell what this specific endpoint does that the others don't. The verb+resource pair is effectively missing.

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?

It gives a generic motivation ('Vet x402 sellers before you pay') but no condition under which an agent should call history versus x402index__audit, __verdict, __dossier or __pick. The mention of '/pick finds the right paid endpoint' points at another tool without saying when this one is the right choice. Usage is implied at best, and arguably misdirected.

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?