Skip to main content
Glama

Loyal Spark Holder

Bazaar Discover Resources

bazaar_discover_resources
Read-onlyIdempotent

Discover third-party x402-paid resources in Coinbase CDP's Bazaar registry. Read-only.

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_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text filter
limitNoMax rows (default 25, max 100)
cursorNoPagination cursor from a previous discover_resources response
networkNoe.g. 'base'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so 'Read-only' simply repeats structured data. The description does add that results are third-party and x402-paid from an external registry (consistent with openWorldHint), but says nothing about rate limits, registry freshness, or what a returned 'resource' contains. No contradiction with annotations.

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?

Two short sentences, front-loaded with the core purpose and scope, with zero filler. The second sentence is arguably redundant given the annotations, but it costs almost nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should convey what a discovery call returns (a paginated list of resources, apparently, given the cursor param) and whether results are filtered by payment capability. Annotations and schema cover safety and inputs well, so the remaining gap is moderate rather than severe.

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% and all four parameters are already documented in the schema, including the limit default/max and the provenance of the cursor. The description adds no syntax, format, or matching behavior for 'q' or 'network', 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 ('Discover'), resource ('third-party x402-paid resources') and the exact registry ('Coinbase CDP's Bazaar registry'), which is far more than the title. It only partially distinguishes itself from the near-identical sibling bazaar_discover_mcp_servers, which must be inferred from the word 'resources' 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 Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative pointer. The closest thing to guidance is the 'Read-only' tag, which is a safety property rather than a selection rule, leaving the agent to guess between this and bazaar_discover_mcp_servers.

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