grokbot.tools

Get one Grok Bot connector

get_connector

Read-onlyIdempotent

Get the full public record for one published connector by its slug (the last part of https://grokbot.tools/connectors/{slug}): summary, install method with step-by-step instructions and sources, MCP URL (null for built-in plugins), auth type, docs link, Grok Bot test status with the last test date, notes, related wishlist requests, and the page URL. Status is never 'Verified' unless it was verified inside Grok Bot with a dated test. Read-only.

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": {
      "slug": "<slug>"
    },
    "name": "get_connector"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Connector slug, e.g. 'notion', 'linear', 'context7'. Find slugs with search_connectors.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new semantics: MCP URL is null for built-in plugins, and 'Verified' status is only ever set by a dated test inside Grok Bot — real domain rules an agent could otherwise misread. It does not cover error behavior for an unknown slug.

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?

The purpose and lookup key are front-loaded, followed by the return inventory. The long enumerated field list is slightly heavy, but since there is no output schema it earns its place as the only description of the payload.

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 must carry the return contract, and it does by listing every field returned plus the null/verification semantics. Missing only edge-case behavior (unknown or unpublished slug) and any mention of the sibling tools in prose.

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 coverage is 100% with one parameter, so the baseline is 3. The description still adds meaning by defining the slug as the final segment of https://grokbot.tools/connectors/{slug}, complementing the schema's example values.

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 — retrieve one published connector by slug — and enumerates the exact record contents (install method, MCP URL, auth type, test status, wishlist requests). It is unmistakably distinct from list_connectors and search_connectors, which operate over sets.

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?

Usage is implied: this is the detail fetch for a single connector, and the slug is identified as the last path segment of the connector URL. However, the description never explicitly says when to prefer this over search_connectors or list_connectors, and the routing hint ('Find slugs with search_connectors') lives in the schema, not the description.

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?