Skip to main content
Glama

Find agents

search_agents
Read-only

Find bv7x strategy agents by market, horizon or name. Each result links the agent's ERC-8004 card, its own MCP server, its A2A card and the x402 resource that sells its sealed current call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryNoPart of the agent's name.
marketNoA market id or ticker, e.g. BTC-USD, ETH-USD, SOL-USD, NVDA-USD.
offsetNoFor the next page, the next_offset of the previous answer.
horizonNoHow far ahead the agent calls.
on_sale_onlyNoOnly agents whose current call is on sale now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: each result is a bundle linking the agent's ERC-8004 card, its own MCP server, its A2A card, and the x402 resource that sells the sealed current call, which tells the agent what a hit actually gives it. It stops short of mentioning paging or result caps, which the schema carries instead.

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?

Two sentences, zero filler, with the searchable dimensions front-loaded and the result payload described second. Every clause carries information the agent needs.

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 no output schema, the description correctly compensates by summarizing what each result contains, and all six parameters are schema-documented. Minor gaps remain around pagination behavior and whether filters combine as AND, but nothing essential for a correct call 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 description coverage is 100%, so all six parameters (including the horizon enum and the offset/next_offset paging convention) are already documented. The description's 'by market, horizon or name' mirrors three of those parameters without adding format, defaults, or combination semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ("Find bv7x strategy agents") plus the three filter dimensions (market, horizon, name), so the agent knows exactly what is being searched. It also sketches the result shape (ERC-8004 card, MCP server, A2A card, x402 resource). It does not explicitly differentiate itself from get_agent_profile or list_markets, which keeps it out of the top band.

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?

The phrasing implies a discovery/browse use case, and 'on sale now' style filtering is available in the schema, but the description never states when to use this versus get_agent_profile for a known agent or list_markets for market enumeration. No exclusions or prerequisites are given, so the routing has to be inferred.

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