x402 Bazaar

basename

Read-onlyIdempotent

Resolve names ↔ addresses on Base — Forward + reverse Basename resolution read from the Base L2 Resolver: turn jesse.base.eth into an address, or an address into its primary Basename. No API key required. Required input: query. Priced $0.01 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.

Input Schema

Name	Required	Description	Default
`query`	Yes	Basename or 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 read-only, idempotent, non-destructive behavior, but the description adds genuinely useful operational context: $0.01 per call via x402 on Base, prepaid x-credit-token header for unlimited calls, and 1 free call/day. That payment/auth profile is not derivable from annotations or schema.

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?

Front-loaded and appropriately brief, but it wastes space by repeating 'No API key required' verbatim at the start and end, and packs pricing into the same dense sentence as the core function. Trimming the duplicate would tighten it without losing information.

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?

An output schema exists, so return-value documentation is not required, and the description covers input, chain, resolver, cost, and auth. Minor gaps remain, such as behavior when a reverse record or primary Basename does not exist, but nothing essential to invoking the tool is missing.

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 'query' param is documented as 'Basename or address'), so the baseline is 3. The description's 'Required input: query' merely restates what the schema already declares and adds no syntax, format, or edge-case detail (e.g., normalization, namehash handling).

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?

States a specific verb+resource (Basename resolution on Base) and explicitly covers both directions (forward and reverse), naming the mechanism (Base L2 Resolver). This is distinguishable from siblings like ens_resolve (Ethereum) and basename_profile (profile data rather than name-to-address mapping).

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

Usage Guidelines3/5

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

The forward/reverse examples ('turn jesse.base.eth into an address, or an address into its primary Basename') imply when the tool is used, and payment details help an agent decide feasibility. However, it never names alternatives such as ens_resolve or basename_profile, nor states exclusions, so routing guidance is only implied.

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?