Skip to main content
Glama

Loyal Spark Holder

Bazaar Discover MCP Servers

bazaar_discover_mcp_servers
Read-onlyIdempotent

Search Coinbase CDP's Bazaar MCP catalog (search_resources) for third-party x402-payable tools. Read-only, free. Rows are run via the Bazaar MCP server's proxy_tool_call, not here.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch text, e.g. 'weather' or 'loyalty'
limitNoMax rows (default 20, max 20)
cursorNoIgnored: CDP search has no cursor. Narrow with q/network.
networkNoNetwork: 'base', 'base-sepolia', or CAIP-2 like 'eip155:8453'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by adding that calls are free/no-cost and that results are a discovery listing only — execution must go through proxy_tool_call on the Bazaar MCP server, which is non-obvious lifecycle context. It does not describe row shape or result fields.

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?

Three short sentences, front-loaded with the action and immediately followed by the cost/safety note and the execution boundary. Almost nothing is wasted; the parenthetical '(search_resources)' is minor implementation detail but still aids identification.

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 full schema coverage and rich annotations, the description covers the two things structured data cannot: that this is free and that results must be executed elsewhere. The remaining gap is return shape — there is no output schema, and the description only implies rows contain callable tools rather than describing fields or pagination.

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%, so q, limit, cursor and network are already fully documented, including that cursor is ignored. The description adds no query syntax, network default, or limit behavior beyond what the schema states, so the baseline of 3 applies.

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: search Coinbase CDP's Bazaar MCP catalog for third-party x402-payable tools, and names the underlying API (search_resources). An agent can tell this is a discovery/search tool rather than an execution tool. It does not name or distinguish itself from the sibling bazaar_discover_resources, so it falls short of a 5.

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 sentence 'Rows are run via the Bazaar MCP server's proxy_tool_call, not here' is explicit when-not guidance and points at the follow-up step, which is the main misuse risk for a discovery tool. 'Read-only, free' adds a cost/safety precondition. It stops short of naming the sibling alternative (bazaar_discover_resources) that an agent would otherwise have to compare against.

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