Fetch recent transcript entries for a Grok Bot agent by specifying its agent ID. Limit results, select a session, or retrieve before a sequence number.
Recent transcript entries (entry_public shape). Default limit 40, max 100.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| agent_id | Yes | ||
| before_seq | No | ||
| session_id | No | Chat session id; default empty MAIN transcript |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already tells the agent this is a safe read. The description usefully adds a hard cap (max 100) that the schema does not express, plus the default. However, it says nothing about ordering, pagination via before_seq, or what a transcript entry contains beyond the shape name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two terse fragments with the return shape front-loaded and the limit constraint following. Nothing is wasted, though the telegraphic style trades clarity for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should carry more of the return and pagination story, but it only names the entry_public shape. before_seq's role in cursor-style paging, agent_id semantics, and when to reach for this transcript are all missing for a 4-parameter read tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 25% (session_id alone is documented). The description compensates partially by clarifying the limit default and max 100, which the schema omits, but agent_id and especially before_seq remain entirely unexplained in both places.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
It identifies the resource (transcript entries) and notes the return shape (entry_public), but there is no explicit verb and no differentiation from siblings like grokbot_pending or grokbot_status that also surface agent activity. An agent can roughly infer 'read history' but not clearly where this fits among the 20 sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use guidance, no conditions for choosing it over grokbot_pending or grokbot_status, and no mention of prerequisites. The word 'Recent' is the only hint of intended usage, which the agent must infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.