Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

x402index__batchcheck

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

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

Input Schema

NameRequiredDescriptionDefault
taskNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / base
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / limit
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / base
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / resource
      Removed value: -{
-  "type": "string"
-}
  3. Changed2 schema fields changed
    • addedInput schema / properties / resource
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / resources
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
  4. Changed3 schema fields changed
    • removedInput schema / properties / budget_usd
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / resources
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  5. Changed3 schema fields changed
    • addedInput schema / properties / budget_usd
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / urls
      Removed value: -{
-  "type": "string"
-}
  6. Changed3 schema fields changed
    • removedInput schema / properties / days
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / resources
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / urls
      Added value: +{
+  "type": "string"
+}
  7. Changed4 schema fields changed
    • 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 (up to 20)",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "urls"
-]
  8. Added

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does deliver important behavior: cost is $0.01 USDC on Base (eip155:8453), payment is transmitted via params._meta["x402/payment"], and the transport is an HTTP GET to a specific URL. What it omits is any statement about response shape, batch size limits, or failure modes — notable gaps for an unannotated tool.

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?

Purpose is front-loaded, and the price/payment/URL details earn their place. The "New: /pick finds the right paid endpoint" sentence is promotional cross-marketing for a sibling tool and dilutes focus, and the run-on first sentence packs three capabilities without structure.

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 2-parameter tool with no annotations and no output schema, the description covers the commercial and transport mechanics well, but leaves the two declared inputs and the return value completely unexplained. An agent knows how to pay but not what to send or what it will get back.

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 compensate, but neither documented parameter ('task' and 'limit') is explained — their meaning and expected values are entirely undisclosed. The only parameter-like detail given is the undocumented payment meta field, which does not resolve the ambiguity of the declared schema.

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 clause states a recognizable goal ("Vet x402 sellers before you pay"), but the rest of the sentence lists three loosely related capabilities (charge decode, fairness vs index, full-catalog audit) plus a cross-promotion of a different endpoint (/pick), so it is unclear what THIS tool actually does versus its siblings like x402index__audit or x402index__verdict. The name 'batchcheck' implies batch verification, which the description never confirms or explains.

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 a pre-payment vetting context, which is real usage guidance, and it points to /pick for a different job. However, it never contrasts this tool with the many adjacent siblings (x402index__audit, verdict, dossier, paycheck, x402check__batch), so the agent must guess when batchcheck is preferable to them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton toolsInspect
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