x402 Bazaar

base_block

Read-onlyIdempotent

Any Base block, by number, hash or tag — One block on Base — height, hash, parent, timestamp and age in seconds, transaction count, gas used against the limit, and the base fee in gwei. Takes a block number, a 0x… block hash, or latest / finalized / safe / earliest. A block that isn't mined yet answers found:false with the reason rather than an error. Raw chain data, no interpretation. Priced $0.002 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
`block`	No	Block number, hash, or tag (default latest)

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.3/5.0

Behavior5/5

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

Annotations already mark this as read-only/idempotent, and the description adds value beyond that: unmined blocks return found:false with a reason rather than an error, results are raw chain data with no interpretation, and access details (x402 pricing, x-credit-token header, free tier, no key/wallet) are disclosed. No contradiction with annotations.

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 description is dense and front-loaded, with core behavior first and pricing/auth last. It is longer than minimal, but each sentence carries operational information; only minor redundancy like 'On Base' repeated in the pricing sentence.

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?

For a single-optional-parameter read-only tool with an output schema, the description covers purpose, accepted inputs, edge cases, data semantics, and access requirements. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, and the description enhances it by enumerating the valid tags (latest/finalized/safe/earliest) and specifying the 0x… hash format. It doesn't go into block-number formatting, but the schema plus description is sufficient.

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?

The description states the resource precisely — one Base block by number, hash, or tag — and enumerates the returned fields (height, hash, parent, timestamp, gas, base fee). It is clearly distinct from sibling transaction/receipt/status tools, though it never uses an explicit operation verb like 'get' or 'fetch'.

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?

It gives concrete usage context: accepted identifiers (block number, 0x hash, latest/finalized/safe/earliest) and the unmined-block edge case returning found:false. It doesn't explicitly say when not to use it or name alternative tools, but the usage conditions are clear enough.

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?