scout-mcp

bazaar_search

Find AI-agent APIs with micropayment access from the x402 Bazaar. Enter a query to search the CDP Discovery directory and get matching APIs with price, network, and relevance score.

Instructions

Search x402 Bazaar for AI-agent APIs with micropayment access. Queries the CDP Discovery directory of x402-enabled HTTP resources. Returns matching APIs with price, network, and relevance score.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "bazaar_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query (matched against API URL and description)
`per_page`	No	Max results to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description bears full burden. It mentions return fields and data source but does not discuss rate limits, authentication, pagination behavior, or potential empty results. Adequate but not rich.

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?

Three sentences, zero waste. Each sentence adds new info: what it does, where it searches, what it returns. Front-loaded with action verb.

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?

Given no output schema, description explains return fields adequately. Tool has 2 simple params, no nested objects, and no enums. Description covers core functionality, though could mention pagination or error cases.

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 baseline is 3. Description does not add extra semantics beyond schema: query matched against URL and description, per_page defaults to 10 and has min/max. No enrichment needed.

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?

Description clearly states the tool searches x402 Bazaar for AI-agent APIs with micropayment access, specifies it queries CDP Discovery directory, and lists return fields (price, network, relevance score). Distinguished from siblings by unique domain.

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?

No explicit guidance on when to use this vs alternatives, but sibling names suggest distinct search domains (e.g., arxiv_search, reddit_search). Implied usage: use for x402-enabled APIs. No exclusions or prerequisites mentioned.

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