x402 Bazaar

b20_batch

Read-onlyIdempotent

Freeze/seize scan for up to 5 B20 tokens — Runs the B20 safety verdict across up to 5 B20 tokens in one call — each scored for freeze/seize/pause/rebase/uncapped-mint, with the worst score surfaced. For portfolio holders and agents screening several B20s at once. Required input: addresses. Priced $0.08 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 wallet or API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`addresses`	Yes	B20 addresses (comma-separated)

Output Schema

TableJSON 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. Dates show when Glama detected each change.

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"
-]
```
AddedAug 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior; the description then adds meaningful context: the worst-score aggregation, the per-call cost, the x-credit-token payment option, free-tier limit, and that no wallet or API key is needed. This goes well beyond the structured annotations without contradicting them.

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

Conciseness4/5

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

The core purpose is front-loaded and the description is information-dense without being bloated. Minor redundancy exists between 'Freeze/seize scan' and the repeated list of scoring dimensions, but every sentence contributes useful operational or pricing context.

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

Completeness5/5

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

Given the simple one-parameter input schema, high schema coverage, and existing output schema, the description provides everything an agent needs to invoke the tool: purpose, cardinality limit, input requirement, pricing/authentication model, and safety profile. No critical operational detail is missing.

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

Parameters4/5

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

The input schema fully documents the 'addresses' parameter format (comma-separated B20 addresses), so the baseline is 3. The description adds a valuable constraint not in the schema: the batch supports 'up to 5' tokens, and clarifies the evaluation dimensions (freeze/seize/pause/rebase/uncapped-mint).

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

Purpose5/5

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

Clearly states a specific action ('freeze/seize scan') and resource ('up to 5 B20 tokens'), then adds scoring dimensions. It differentiates from single-token siblings like b20_safety by emphasizing the batch capability and the one-call nature.

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?

Explicitly scopes usage to 'portfolio holders and agents screening several B20s at once,' giving clear context for when the batch tool is appropriate. It does not explicitly name a single-token alternative or state when not to use it, so it loses a point.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Despite excellent per-tool descriptions, the set contains many near-overlapping tools: rug_score, batch_risk, pre_trade_gate, and deep_dd all assess token risk; wallet_portfolio, wallet_networth, and wallet_tokens all list balances; b20_safety, b20_gate, and b20_dossier overlap heavily; url_extract, web_extract, ai_extract, and url_to_json also blur boundaries. An agent would struggle to consistently pick the right tool without reading every description.

Naming Consistency4/5

Naming is overwhelmingly consistent snake_case verb_noun (token_price, rug_score, address_trust, file_convert, safe_to_send). Minor deviations: noun-only names like holders, basename, deep_dd, business_days, and new_tokens, plus the abbreviation deep_dd, slightly break the pattern.

Tool Count1/5

137 tools is far beyond the 50+ extreme-mismatch threshold. Even as a marketplace bazaar, this is an enormous, unwieldy surface where many tools overlap and each contributes only a sliver of unique value.

Completeness4/5

For the apparent purpose — a pay-per-call bazaar covering on-chain analysis, wallet intelligence, token due diligence, plus generic text/web/finance utilities — the surface is extensive and covers most read-only workflows with few dead ends. Minor gaps exist (no historical price series, no swap execution, no true on-chain write actions), but the set is not severely incomplete for its stated niche.

Resources

Need Help?