Skip to main content
Glama

Get Grok Bot result

get_grok_result

Retrieve the result of a previously submitted Grok task by request_id, returning pending status if unfinished or completed output and artifact references when ready.

Instructions

Look up a previously submitted task by request_id. Returns the result, or status pending if it is not ready yet. A finished result may include an artifacts array (detailed files such as Markdown reports, JSON, CSV or XLSX). The answer is only a summary: when artifacts are listed, call download_grok_artifacts and read the files for the full detail.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_grok_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id returned by ask_grok or submit_grok_task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behaviors: it may return a pending status rather than a result, and a finished result may contain an artifacts array plus a summary answer. It does not cover polling cadence, result retention/expiry, or error behavior for an unknown or expired request_id.

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?

Four short sentences, front-loaded with what the tool does and what it returns, then the actionable routing advice about artifacts. Every sentence carries distinct information with no padding.

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?

No output schema exists, so the description must explain return values, and it does: result versus pending status, artifacts array contents, and the summary-only nature of answer. It is nearly complete for a simple one-parameter lookup, missing only failure/expiry semantics.

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?

There is a single required parameter with 100% schema description coverage, and the schema already states that request_id comes from ask_grok or submit_grok_task. The description repeats that the lookup is by request_id without adding format, syntax, or edge-case meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('Look up a previously submitted task by request_id') plus what it returns, which is far beyond restating the name. It distinguishes itself from download_grok_artifacts by pointing to that tool for file contents, but it does not explicitly contrast itself with ask_grok or submit_grok_task.

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?

Gives a clear use condition (retrieving a task previously submitted) and an explicit handoff rule: when artifacts are listed, call download_grok_artifacts and read the files. It lacks an explicit when-not-to-use statement, such as telling the agent not to poll this instead of using ask_grok for new work.

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