Skip to main content
Glama

Find bots

bots_discover
Read-onlyIdempotent

Returns verified bots in the bots.theta store: name, .theta name, pitch, category, price_tfuel, free_per_day, official, listing_ref. Use bots_discover to find bots, then bots_inspect for one bot's details, then bots_call to ask it. Read-only, free, no key. No match: count 0.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords to match in name, pitch, .theta name, category or tags, e.g. "tax" (max 100 chars)
limitNo1-50, default 20
categoryNoOnly bots in this category (case-insensitive, as shown in each result's category)

Output Schema

NameRequiredDescriptionDefault
botsNo
blockNo
countNo
staleNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Only bots in this category (case-insensitive, as shown in each result's category)"
    • addedInput schema / properties / category / maxLength
      Added value: +40
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / description
      Added value: +"1-50, default 20"
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / q / description
      Previous value: -"Words to match"New value: +"Words to match in name, pitch, .theta name, category or tags, e.g. \"tax\" (max 100 chars)"
    • addedInput schema / properties / q / maxLength
      Added value: +100
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "bots": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "count": {
      +      "type": "integer"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds cost and auth context ('free, no key') and empty-result semantics ('No match: count 0'), which an agent cannot get from the structured fields. It stops short of describing pagination or result ordering, so it is strong but not exhaustive.

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?

Three short sentences: what it returns, how it fits the workflow, and operational constraints. Front-loaded with the resource and result shape, zero 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?

The tool is simple (0 required params, fully documented schema, an output schema, and clear annotations) and the description covers purpose, workflow position, cost/auth, and the empty-result case. Nothing an agent needs in order 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%, with q, limit and category each documented including defaults, ranges and matching behavior. The description adds no parameter-level meaning beyond that, so the 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 and resource ('Returns verified bots in the bots.theta store') and enumerates the returned fields (name, .theta name, pitch, category, price_tfuel, free_per_day, official, listing_ref), which unambiguously separates it from bots_inspect and bots_call. An agent can identify the tool without opening the schema.

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?

Gives an explicit three-step routing chain: use bots_discover to find bots, then bots_inspect for one bot's details, then bots_call to ask it. Each sibling is named with the condition that selects it, so nothing is left to inference.

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