x402 Bazaar

holders

Read-onlyIdempotent

Top holders, concentration & LP lock — Top-10 holders with their %, holder count, concentration level (whale risk), and LP-lock %, from GoPlus. Lets agents judge how fairly a token is distributed before trading. No API key required. Required input: address. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "holders"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Token contract address

Output Schema

Name	Required	Description
`data`	No	The result payload. Shape is service-specific; every field is documented in the tool description.
`service`	No	The service id that answered.
`checkedAt`	No	ISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 31, 2026

changedOutput schema / properties / data / description

Previous value: -"The result payload. Shape is service-specific; every field is documented in the service description above."New value: +"The result payload. Shape is service-specific; every field is documented in the tool description."

Changed1 schema field changedAug 31, 2026
- removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```

Changed1 schema field changedAug 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {
+      "description": "ISO-8601 timestamp of when the underlying reads were taken.",
+      "type": "string"
+    },
+    "data": {
+      "description": "The result payload. Shape is service-specific; every field is documented in the service description above.",
+      "type": "object"
+    },
+    "service": {
+      "description": "The service id that answered.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJul 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new operational context: no API key needed, $0.02/call over x402 on Base, the prepaid x-credit-token header for unlimited calls, and 1 free call/day. It does not mention rate limits beyond the free tier or failure modes, so it falls short of 5.

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 and outputs are front-loaded well, but the pricing paragraph is bloated and "No API key required" is repeated verbatim in two places, which is avoidable waste in a short description.

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

Completeness4/5

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

With an output schema present, return values need not be described; the description covers what data comes back, the source, the cost/auth model, and the required input. The only gap is chain/address-format scope for the single parameter, which is minor.

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

Parameters3/5

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

Schema description coverage is 100% (the single address parameter is documented as "Token contract address"). The description only restates it as "Required input: address" and adds no format, chain, or validation meaning. Baseline 3 is correct.

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

Purpose4/5

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

States a specific resource (top holders, concentration, LP-lock) with concrete outputs (Top-10 with %, holder count, whale-risk level) and names the data source (GoPlus). This clearly separates it from siblings like holder_forensics, holder_overlap, or lp_lock, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Lets agents judge how fairly a token is distributed before trading" gives a clear pre-trade use context. There are no explicit exclusions or named alternatives (e.g. when to prefer lp_lock or holder_forensics instead), so it stops short of full when/when-not guidance.

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

All x402 Bazaar 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?