Skip to main content
Glama

Arbiter x402 Market Intel

Demand map of the paid x402 economy ($0.20)

market_map
Read-onlyIdempotent

Before choosing what to build or how to price it: 20 categories with listings, sellers, 30-day payers and paid calls, estimated gross, leader share, gap score and verdict, the biggest opportunities, price bands, Base vs Solana and the most-paid listings. Optional category (deep dive) and network. No parameters needed. PAID: $0.20 per call, no account. Pay with x402 over MCP (USDC on Base), or with a Route Pass (header Authorization: Bearer ap1...). An unpaid call returns the payment terms and charges nothing; bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/market.

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": "market_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoall (default) | base | solana: only listings that accept this network
categoryNoOptional deep dive into one category: x402-test, wallet-exec, token-risk, compliance, prediction, people-data, social, weather-geo, fin-trad, market-data, onchain-data, web-search, web-scrape, llm, media-gen, news-research, agent-infra, dev-tools, real-world, other (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description's real value is payment mechanics — $0.20 per call, no account, x402 USDC on Base or a Route Pass bearer header, unpaid calls return terms and charge nothing, bad input rejected before payment, failed work never charged — but it omits any note on response size or rate limits.

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?

Usage context is front-loaded, then contents, then parameters, then payment terms — a sensible order with no filler sentences. The single dense paragraph is longer than necessary, but each clause carries distinct 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?

With no output schema, the description compensates by enumerating the returned fields and the network comparison, and it fully covers billing, pre-payment validation and failure-charge behavior. Only the response shape and volume are left unstated, which is a minor gap for a read-only report tool.

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% and both parameters are enums with their own descriptions, so the description only has to add framing. It does note that both are optional with defaults and that category triggers a deep dive, but it adds no semantics beyond the schema's own enum lists.

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?

The title and opening enumerate exactly what the resource contains: 20 categories with listings, sellers, 30-day payers, paid calls, gross, leader share, gap score, price bands, network split and top listings. It is specific enough to distinguish it from a raw-listings tool, though it never names a sibling such as market_peek, so an agent must infer the difference from price and scope alone.

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?

"Before choosing what to build or how to price it" gives a concrete decision context, and "Optional category (deep dive) and network. No parameters needed" tells the agent the tool works with zero args. It stops short of naming an alternative for a cheap first look, so the when-not-to-use case is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources