Skip to main content
Glama
Sign In

bots

by net.urbot
OverviewDiscussionsAdmin

Search URBot bots

search_bots

Keyword-search the URBot catalog across bot names, taglines, categories, knowledge topics, and capability pitches. Returns the top matches with slug, name, category, price, and why they matched. Use this first when you know the task but not which expert bot to use (e.g. "sourdough", "tax deductions", "unreal engine blueprints", "knee pain").

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

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text keywords, e.g. "meal prep nutrition"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that it searches across multiple fields, returns top matches, and lists returned fields. It doesn't cover pagination or ordering, but for a search tool the behavior is reasonably clear.

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, front-loaded with the action and key details. No superfluous words. Every sentence adds value.

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?

Given the tool's simplicity (one parameter, no output schema), the description is fully adequate. It covers what is searched, what is returned, and provides usage examples.

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 covers 100% of parameters with a basic description. The description adds value by providing concrete examples ('sourdough', 'tax deductions') and clarifying the parameter's role, exceeding baseline 3.

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?

The description explicitly states it keyword-searches the URBot catalog across multiple fields and returns top matches with specific fields. It clearly distinguishes from siblings like list_bots (listing all) and get_bot (fetching by identifier).

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?

The description explicitly advises 'Use this first when you know the task but not which expert bot to use', providing clear context. It does not explicitly state when not to use or list alternatives, but the context and sibling names imply those alternatives.

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

All bots toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources