x402 Bazaar

base_nonce

Read-onlyIdempotent

How many transactions has this address sent? — The next nonce for any Base address, plus its ETH balance and whether it is a contract. The count means different things either side of that line — transactions sent for a wallet, contracts deployed for a contract — so both are reported under their own name instead of one ambiguous number. What you need before building a transaction, or to tell a fresh address from a used one. Required input: address. 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
`address`	Yes	Address

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.

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 declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds genuinely useful behavior: the nonce count is interpreted differently for wallets vs contracts and both are reported under their own names. It also discloses input requirements and pricing/auth model, going well beyond 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 front-loaded with the core purpose and includes useful operational details like pricing and authentication. Every part contributes to invoking the tool correctly, though the free-call and credit-header details are slightly dense.

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 schema and rich annotations, the description covers input, semantics, use cases, chain, pricing, and auth. The presence of an output schema means return values need not be described. Nothing essential 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 schema only describes address as 'Address', but the description clarifies it must be a Base address and explains that it can represent either a wallet or a contract. This adds meaning beyond the schema despite 100% schema coverage.

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?

Description clearly identifies the resource (any Base address) and the specific data returned: next nonce, ETH balance, and contract status. It also disambiguates the nonce meaning for wallets versus contracts, which distinguishes it from generic address tools and prevents misinterpretation.

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?

States explicit use cases: 'before building a transaction' and 'to tell a fresh address from a used one.' It does not name alternative tools or exclusions, but the context is clear enough for an agent to select it appropriately among siblings.

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?