Skip to main content
Glama

Message Grok Bot

grok_send

Sends a message to a Grok Bot desktop bot and waits for its reply; if the bot is still working when the wait ends, retrieve the rest later.

Instructions

Send a message to a bot in the Grok Bot desktop app and wait for its reply. Grok Bot is an agent that can browse the web, make phone calls, send email, and run routines, so it may act on the message. If it is still working when the wait ends, call grok_read later to get the rest.

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": {
      "message": "<message>"
    },
    "name": "grok_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
botNoBot name or id (default: the bot currently open)
messageYesWhat to say to the bot
wait_secondsNoHow long to wait for the reply (default 120, 0 = do not wait)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it discloses the most important non-obvious trait: the bot is an agent that can browse the web, make phone calls, send email, and run routines, so it may take real actions on the message. It also discloses that this call blocks and waits. It omits details such as permissions, failure modes, and side-effect confirmation, which keeps this from being a 5.

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, both meaningful: the first states the action and the wait, the second states the side-effect risk, and the third states the continuation path. The action is front-loaded and nothing is padded.

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?

For a 3-parameter tool with no annotations and no output schema, the definition covers what the tool does, what it returns conceptually (a reply), the blocking behavior, the side-effect risk, and the fallback for incomplete replies. It does not cover error conditions or empty-reply behavior, which is a modest gap rather than a blocker.

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%, so the schema already documents bot, message, and wait_seconds, including the default and the meaning of 0. The description slightly reinforces the wait semantics through 'wait for its reply' and 'when the wait ends', but adds no syntax or format detail beyond the schema. A baseline 3 is appropriate.

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 definition opens with a specific verb and resource ('Send a message to a bot in the Grok Bot desktop app') and states the waiting behavior. It also implicitly separates this tool from grok_read by saying to call grok_read only for the remainder after the wait ends, so an agent can distinguish the two without opening either 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?

The definition gives clear routing guidance for the most important case: if the bot is still working when the wait ends, call grok_read later to get the rest. It does not spell out explicit exclusions (for example, 'use grok_read alone if you only want to poll'), but the condition that selects the sibling tool is stated directly.

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