Skip to main content
Glama

x402 Bazaar Rank

by io.github.mike-lblc
OverviewDiscussionsAdmin

Search x402 services

search_x402_services
Read-onlyIdempotent

Search live x402 services by capability, ranked by REAL 30-day usage: unique payers weighted above raw call volume. Covers every service in the public index. Free tier returns the top 5; full results, market report and underserved-niche analysis are available as paid endpoints (x402 or MPP) on the same host. Not for picking one service for a concrete task (use best_service_for_task), for market-wide totals (use x402_market_stats) or for this host's own products (use list_paid_data_products).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYescapability to look for, e.g. 'web search', 'llm inference'
networkNooptional CAIP-2 filter, e.g. eip155:8453
include_testnetsNoalso list services that exist only on test networks (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_testnets
      Added value: +{
+  "description": "also list services that exist only on test networks (default false)",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, openWorld, non-destructive); the description adds genuinely non-obvious behavior: results are capped at the top 5 on the free tier, fuller results/market report/underserved-niche analysis sit behind paid x402 or MPP endpoints on the same host, and ranking is usage-weighted rather than raw-volume. These are exactly the traits an agent needs before deciding whether a call is sufficient.

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?

Single dense paragraph, front-loaded with the verb/resource/ranking before the freemium caveat and the sibling routing. Nearly every clause earns its place, though the parenthetical enumeration of three alternatives makes it longer than strictly necessary.

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?

No output schema exists, so the description carries return-value burden and does disclose the free-tier result cap and paid escalation path. It does not describe the shape of a returned service record or whether results are paginated, but nothing essential to invoking the tool correctly 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% for all three parameters, so the schema already explains query, network (CAIP-2) and include_testnets semantics. The description adds no per-parameter syntax, and its usage commentary concerns result ranking rather than inputs; baseline 3 is correct.

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 (Search) and resource (live x402 services), plus the ranking basis (REAL 30-day usage, unique payers weighted above raw call volume) and index coverage. It explicitly names the three siblings it is not (best_service_for_task, x402_market_stats, list_paid_data_products), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Goes beyond context to explicit exclusions: 'Not for picking one service for a concrete task (use best_service_for_task)', 'for market-wide totals (use x402_market_stats)', 'or for this host's own products (use list_paid_data_products)'. Each alternative is paired with the condition that selects it.

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

All x402 Bazaar Rank toolsInspect
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