Skip to main content
Glama

Read Grok Bot chat

grok_read

Read recent messages in a Grok Bot chat and check whether the bot is still working. Optionally wait for the bot to finish before returning the latest replies.

Instructions

Read the latest messages in a Grok Bot chat (also shows whether the bot is still working).

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

Input Schema

NameRequiredDescriptionDefault
botNoBot name or id (default: the bot currently open)
countNoHow many recent messages (default 10)
wait_until_idle_secondsNoIf the bot is working, wait up to this long for it to finish first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does disclose a non-obvious trait — that the response also indicates whether the bot is still working — but it says nothing about permissions, safety of the read, message format, or truncation behavior.

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?

A single front-loaded sentence with no wasted wording; the core action comes first and the secondary capability is parenthetically subordinated where it belongs.

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 three-optional-parameter read tool with no annotations and no output schema, the description covers the essentials of the action but leaves the response shape (what a 'message' contains), the count cap behavior, and the idle-wait mechanics to the schema. Adequate but not complete.

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 all three optional parameters documented including defaults and ranges, so the baseline is 3. The description adds only the implicit link between 'whether the bot is still working' and wait_until_idle_seconds, without explaining that relationship explicitly.

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 names a specific verb and resource — 'Read the latest messages in a Grok Bot chat' — which an agent can distinguish from grok_send (write) and grok_list_bots (enumerate bots). It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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: the tool reads recent messages from a bot chat, and the parenthetical hints at a status-check use case. There is no explicit statement of when to prefer this over grok_send or grok_list_bots, and no preconditions are stated.

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