Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

x402index__demandreport_json

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.json

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

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. Added
  3. Removed
  4. Added
  5. Removed
  6. 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 to vet (up to 20). POST body may instead be {\"urls\": [...]}",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "urls"
-]
  7. Changed2 schema fields changed
    • 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"
+]
  8. Changed4 schema fields changed
    • 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"
-]
  9. Changed1 schema field changed
    • addedInput schema / properties / resources
      Added value: +{
+  "description": "Batch: up to 25 endpoint URLs in one call",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  10. Changed3 schema fields changed
    • 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"
+]
  11. Added

TDQS

C2.6/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 meaningful operational facts: cost ($0.01 USDC on eip155:8453), the payment channel (params._meta["x402/payment"]), and the HTTP endpoint/method. However, it says nothing about what the report returns, whether the call is read-only or stateful, or any rate limits, leaving the behavioral profile half-covered.

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?

The purpose is front-loaded and pricing/endpoint details are compact, but the 'New: /pick...' sentence is promotional and refers to a different tool, adding confusion rather than value.

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 paid, multi-purpose tool with no output schema, no annotations, and zero parameter documentation, the description covers payment mechanics but omits what the response contains and what the two inputs mean. An agent still lacks enough to call it correctly.

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 parameters. 'task' is only mentioned incidentally in the unrelated /pick sentence, and 'limit' is never explained at all, so the description fails to compensate for the empty 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 lead phrase 'Vet x402 sellers before you pay' gives a verb and a resource, but the tool is named demandreport_json and the description never explains what a demand report actually is. It then lists three capabilities (402 charge decode, fairness vs index, full-catalog audit) that read like separate tools, so an agent cannot confidently tell what this one produces versus its siblings.

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 an implied 'use before you pay' context, but no explicit when-to-use, when-not-to-use, or alternatives among the many x402index siblings (dossier, verdict, audit, pick, history, paycheck). The mention of '/pick finds the right paid endpoint' points at another tool rather than clarifying this one's role.

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