Skip to main content
Glama

Agent Exchange router

Search every agent catalog

search_all_catalogs
Read-only

One search over every open agent catalog indexed at https://bazaar.agentexchange.work/universe: the Official MCP Registry, Smithery, npm packages tagged mcp-server and x402, the Apify Store, ClawHub skills, Agentverse agents, the A2A Registry, Hugging Face Spaces tagged mcp-server, the Docker MCP Catalog and x402-list. Returns name, the link to the entry on its own catalog, description, the catalog popularity number and whether it is paid. Without catalog it searches the top entries of each catalog; with catalog= it searches that catalog in full. For priced x402 routes use find_resources.

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

Input Schema

NameRequiredDescriptionDefault
limitNodefault 30
queryYeswhat you need: words, a product name, a protocol
catalogNooptional: mcp-registry | smithery | npm-mcp | npm-x402 | apify | docker-mcp | x402-list | clawhub | agentverse | a2a-registry | hf-mcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and world scope, and the description adds substantive behavior beyond them: the indexed sources, that the default search is depth-limited to top entries, and that the catalog parameter switches to full-depth search. It does not describe ranking or result ordering. Minor tension: openWorldHint=false while the tool aggregates many external catalogs, though those are a fixed index set.

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?

Front-loads the core claim, then scope, then result fields, then the fork to the sibling tool. The long enumeration of eleven catalogs is the only padding, and it is partly redundant with the catalog parameter's list, but it does convey search coverage.

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, and the description compensates by naming the returned fields (name, link, description, popularity, paid). Together with the schema-documented limit default of 30, an agent can call it correctly; only result ordering and total-count behavior remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning the schema lacks: it explains what the catalog parameter changes (full catalog scan versus top entries) and what the query is meant to contain. The enumerated catalog names also contextualize the key values beyond the schema's bare list.

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 and resource ('One search over every open agent catalog') and then enumerates exactly which catalogs are indexed, plus what fields come back. It also distinguishes itself from find_resources for priced x402 routes, so an agent can separate the two without opening a schema.

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?

Gives concrete mode selection: with no catalog it searches top entries per catalog, and with catalog=<key> it searches that catalog in full. It also routes priced x402 lookups to find_resources. It stops short of advising how to pick between querying all catalogs versus one specific key.

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