automaton

x402index__audit

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

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

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"
+}
```
AddedNov 6, 2026

TDQS

B3/5.0

Behavior4/5

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

With zero annotations, the description carries the full burden and does disclose genuinely important behavior: the exact price ($0.01 USDC on Base, eip155:8453), the payment transport (x402 payment block in params._meta), and the concrete HTTP method and endpoint. What it omits is the response shape and what happens if payment is absent or the audit finds a bad seller, which matters for a paid vetting call.

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

Conciseness3/5

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

It is short and leads with the value proposition, but it crams promotion for another endpoint, pricing, and a raw URL into three sentences. The "New: /pick ..." clause does not help an agent invoke this tool and is the weakest use of space.

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?

No output schema, no annotations, and zero parameter documentation mean the description must do more. It never states what an audit returns (a verdict? a fairness score? a decoded charge?), how the two optional parameters shape the call, or what a failure/payment-required path looks like — significant gaps for a paid tool whose siblings include verdict/dossier/pick variants.

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%, so the description must explain `task` and `limit` — and it explains neither. The one mention of "task" is attached to the sibling /pick endpoint, which actively misleads about what the `task` parameter on this tool does, and `limit` is never referenced at all.

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 opening verb phrase "Vet x402 sellers before you pay" is a clear verb+resource, but the sentence then bundles three distinct capabilities (live 402 charge decode, fairness vs a 59k-listing index, full-catalog audit) without making clear which of those this specific `audit` tool performs. It also promotes a sibling endpoint ("/pick") inside its own description, which blurs whether that capability lives here or elsewhere.

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 (pre-payment due diligence), which is useful context. However, it never names an alternative among the many adjacent siblings (x402check__check, x402_preflight__verify, pageaudit__vet, x402index__verdict), and the mid-description pointer to /pick is a cross-sell rather than an explicit when-not-to-use-this rule.

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?