Skip to main content
Glama

Search bots

search_bots
Read-only

Search every rated AI bot by name, registry number or 0x wallet, or browse a category. Returns names, categories, trust levels and profile links.

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

Input Schema

NameRequiredDescriptionDefault
queryNoName fragment, bot number, or 0x address.
categoryNoOne of: ai-models, search-web-data, crypto-trading, social-media, images-video, audio-voice, writing-content, compute-storage, security-trust, other.
newest_firstNoSort by newest instead of most reviewed.

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, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds value beyond them by disclosing the result payload (names, categories, trust levels, profile links) and the important scope qualifier that only *rated* bots are indexed, which an agent needs to interpret empty results. It omits pagination/result-limit behavior, keeping it short of a 5.

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, no filler: the first gives capabilities and lookup keys, the second front-loads the return contents. Every clause carries information an agent can act on.

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 and no required parameters, the description usefully compensates by naming the returned fields, and it clarifies the 'rated only' scope. Remaining gaps are minor for a read-only search tool: no keyword search of three zero-required parameters likely doesn't need more explanation, though result-set limits/pagination are unstated.

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 each parameter already carries its own description, including the category enum list and the sort default ('newest instead of most reviewed'), so the baseline of 3 applies. The description restates the query keys with slightly different wording ('registry number', '0x wallet') but adds no syntax, format, or precedence detail (e.g., what happens if both query and category are supplied).

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 (search/browse) and resource (rated AI bots), and enumerates the three lookup keys plus the category-browse mode, which is far more than the name alone conveys. It does not explicitly differentiate itself from siblings by name, but the sibling set (deals, payments, juries, wallets) shares no resource with bots, so confusion risk is low.

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 description implies usage through the two modes ('search ... by name, registry number or 0x wallet, or browse a category'), which does tell the agent how to pick between a text query and a category sweep. It gives no explicit when-to-use, when-not-to-use, or alternative-tool routing guidance, so it remains at the implied level.

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