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 wallet or API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Basename or 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"
-]
```

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

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool's safety profile is covered. The description adds valuable context beyond the annotations: it names the Base L2 Resolver as the source, states no API key is needed, and discloses pricing and rate limits ($0.01/call, x-credit-token header, 1 free call/day). 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 front-loaded with purpose and examples, and the auth/pricing details are genuinely useful. Minor redundancy ('No API key required' appears twice) prevents a perfect score.

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?

With one well-documented parameter, an output schema, and annotations covering the read-only/idempotent behavior, the description supplies all remaining context an agent needs: source resolver, input format, examples, cost, and authentication method. 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?

Schema coverage is 100% for the single query parameter, so the baseline is 3. The description adds meaning by explaining that the query can be either a Basename or an address and by giving a concrete example of the bidirectional behavior, which goes beyond the schema's bare 'Basename or address'.

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?

The description opens with a specific verb-resource pair ('Resolve names ↔ addresses on Base') and immediately gives concrete bidirectional examples ('jesse.base.eth into an address, or an address into its primary Basename'). This makes it easy to distinguish from sibling resolution tools like ens_resolve or basename_profile.

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?

The description gives clear context for when to use the tool: Basename resolution on Base L2, with both forward and reverse directions. It also states required input and access requirements. However, it does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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?