Skip to main content
Glama

Open a Grok bot

grok_select_bot

Switch the Grok Bot desktop app to a different bot by name, partial name, or ID to route prompts to the intended bot.

Instructions

Switch the Grok Bot app to a different bot.

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": {
      "bot": "<bot>"
    },
    "name": "grok_select_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
botYesBot name (or part of it) or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether the switch persists across sessions, what happens if the bot name is ambiguous or not found, whether authentication is required, or what side effects occur. 'Switch the Grok Bot app' is the only behavioral clue.

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 description is a single front-loaded sentence with no wasted wording. It is appropriately short for a one-parameter tool, though its terseness contributes to the behavioral and usage gaps noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with full schema coverage and no output schema, the description is minimally adequate. However, with no annotations, it should do more to explain what 'switch' means operationally, such as state persistence or failure behavior.

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 the schema already documents the sole parameter as 'Bot name (or part of it) or id.' The description adds no additional meaning about matching behavior, ambiguity handling, or required format beyond what the schema provides.

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?

The description states a specific verb and resource: 'Switch the Grok Bot app to a different bot.' An agent can understand it changes the active bot, and the title reinforces that. It does not explicitly differentiate from siblings like grok_list_bots or grok_read, which keeps it from a 5.

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 only implied: 'different bot' suggests changing the currently active bot, likely after identifying one. There is no explicit guidance on when to use this versus grok_list_bots or whether the bot must already exist, so the agent must infer the workflow.

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

Deploy Server

Other Tools