Skip to main content
Glama
brick-blue

brick.blue MCP server

Official
by brick-blue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search agents

search_agents
Read-onlyIdempotent

Find MCP servers and A2A agents on brick.blue by describing the capability you need. Returns ranked JSON results with endpoints, access, price, and matching tools.

Instructions

Finds MCP servers and A2A agents whose tools do what you describe in plain words. Use it whenever you need a capability you do not have; use get_agent afterwards for one result in full, and verify_endpoint when you already have a URL rather than a need. Results are ranked on what the hub measured — answers its checks, open/paid/key-required, price per call — not on what operators claim. Read-only, no account. Returns JSON results[], each with id, name, endpoint, availability, access, price and the matching tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesWhat you need done, e.g. "weather forecast for a city" or "convert pdf to markdown".
limitNoHow many results to return, 1–50 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • changedInput schema / properties / limit / description
      Previous value: -"Results to return (default 10)."New value: +"How many results to return, 1–50 (default 10)."
    • addedInput schema / properties / q / maxLength
      Added value: +300
  2. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Adds value beyond annotations by disclosing the ranking basis (measured answers, availability, access, price per call — not operator claims) and confirming 'Read-only, no account'. Annotations already cover readOnly/idempotent/openWorld, so this enriches rather than duplicates, though it does not mention rate limits or pagination.

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?

Dense and front-loaded: capability framing first, sibling routing second, ranking semantics third, return shape last. Every sentence earns its place with no filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter read-only search with no output schema, the description pre-describes the JSON result fields (id, name, endpoint, availability, access, price, matching tools), which compensates for the absent output schema. Nothing an agent needs to call it correctly is missing.

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 already documented in the schema, including examples and defaults. The description adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 (Finds) and resources (MCP servers and A2A agents) and explicitly frames it as capability-based search on plain language descriptions. Distinguishes from siblings by naming get_agent and verify_endpoint with their respective scopes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit 'use it whenever you need a capability you do not have', plus routing to get_agent for detail and verify_endpoint when a URL is already known. Covers when to use and which alternatives to pick in adjacent situations.

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

Deploy Server

Other Tools