Skip to main content
Glama
Sign In
x402-wallet-mcp

x402-wallet-mcp

by kato9292929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Bazaar resources

list_bazaar_resources
Read-only

Find x402 services in the CDP Bazaar by running ranked natural-language searches or browsing the catalog page by page, then narrow results by network or maximum USD price.

Instructions

Discovers x402 services in the CDP Bazaar. With query (or filters) it runs a ranked search; without, it lists the catalog page by page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bazaar_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (search returns at most 20)
queryNoNatural-language search, e.g. "weather forecast"
offsetNoOffset when listing without a query
networkNoFilter by network, e.g. "eip155:84532" for Base Sepolia
maxUsdPriceNoMaximum price in USD, e.g. "0.05"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful mode behavior (ranked search vs page-by-page listing) but says nothing about result shape, pagination metadata, or the fact that search caps at 20 results, which is only in the schema.

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

Conciseness5/5

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

Two sentences, zero filler, with the discovery purpose front-loaded and the two operating modes stated compactly. Nothing needs trimming or reordering.

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?

Five optional parameters with no output schema means the description could say more about what a returned resource looks like, but the mode behavior plus rich schema descriptions and read-only annotations cover enough for correct invocation.

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 coverage is 100%, so every parameter is already documented, including the 20-result search cap and offset's listing-only role. The description adds only the nuance that filters as well as `query` trigger ranked search, a marginal gain over the schema.

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?

States a specific verb and resource ('Discovers x402 services in the CDP Bazaar') and implies a catalog-listing tool, which distinguishes it from get_resource_details. It never names a sibling explicitly, so the differentiation is inferential rather than stated.

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?

Gives a clear mode-selection rule: supply `query` (or filters) for a ranked search, omit it to page through the catalog. It does not say when to prefer this over get_resource_details for drilling into a single service, so the exclusion side is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools