grokbot.tools

Search Grok Bot connectors

search_connectors

Read-onlyIdempotent

Search the grokbot.tools directory of MCP connectors and plugins for Grok Bot by name, service or category, with optional filters (Grok Bot test status, install method, auth type). Returns compact summaries with the install method, auth type, honest test-status label and the grokbot.tools page URL; use get_connector for install steps and the MCP URL. Only published directory entries are returned. Read-only; independent fan project, not affiliated with xAI.

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

Input Schema

Name	Required	Description
`limit`	No	Max results, 1-25 (default 10). Larger values are clamped to 25.
`query`	No	Free text matched against connector name, service, category and slug, e.g. 'notion' or 'payments'.
`status`	No	Grok Bot test status. 'verified' = dated test inside Grok Bot. 'seen_working' = seen working, dated re-test pending. 'unknown' = not re-tested inside Grok Bot yet (includes seen_working). 'broken' = failed when tried.
`category`	No	Exact category name, case-insensitive, e.g. 'Developer tools & data', 'Money', 'Design', 'Docs & search', 'Projects & docs', 'Sales & support', 'Files', 'Security'. Use list_connectors with no filters to see categories in use.
`auth_type`	No	'oauth' = you sign in with your own account; 'public' = no sign-in.
`install_method`	No	How the app gets into Grok Bot: built-in plugin (Connect apps), custom MCP URL added via chat, browser only, or unverified.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), yet the description adds genuine context: that only published entries are returned, what each result summary contains, and a scope disclaimer about being an independent fan project unaffiliated with xAI. It stops short of describing pagination or result-count behavior beyond what the schema already encodes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and search dimensions, then the return shape, then the get_connector handoff and scope caveat. It is a dense multi-clause sentence that borders on long, but every clause carries actionable information and nothing is padded.

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?

No output schema exists, so the description carries the burden and does so: it names the return fields (install method, auth type, test-status label, page URL), the filtering constraint, and where to go for follow-up detail. For a six-parameter optional-filter search tool, an agent has everything needed to call it correctly.

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%, and the schema already explains limit clamping, query matching fields, status semantics, category examples and enum meanings. The description only restates the filter groups (test status, install method, auth type) and search dimensions, adding no syntax or format detail beyond the schema. 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 (search) and resource (grokbot.tools directory of MCP connectors and plugins), and scopes the search dimensions (name, service, category) plus optional filters. It also names the sibling get_connector as the tool for install steps, so an agent can separate this from the alternatives without opening any schema.

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?

Explicitly routes to get_connector when install steps or the MCP URL are needed, and states the scope constraint that only published directory entries are returned. It does not directly address when to prefer list_connectors (browse-all) over this search, so one sibling relationship is left implicit.

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

All grokbot.tools tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?