Skip to main content
Glama

Submit Grok Bot task

submit_grok_task

Start a Grok Bot task without waiting and return a request_id immediately; use get_grok_result later to collect the answer.

Instructions

Fire-and-forget: start a Grok Bot task and return a request_id immediately. Use get_grok_result to collect the answer later.

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": {
      "task": "<task>"
    },
    "name": "submit_grok_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
botNoOptional bot name to route the task to.
taskYesThe task for Grok Bot to perform.
contextNoOptional extra context for the bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.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 burden and does disclose the key behavior: submission is asynchronous, returns a request_id right away rather than the answer. It omits side-effect framing (whether a task is queued/persisted), failure modes, and any rate or auth constraints.

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, zero filler, with the async contract stated first and the follow-up tool named second. Every clause earns its place.

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 three-parameter submission tool with full schema coverage and no output schema, the description covers purpose, return handle (request_id), and next step. Minor gap: it never mentions that artifacts from the run are retrieved via download_grok_artifacts, which a caller might need after a successful submission.

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 description coverage is 100%, so bot, task, and context are already documented. The description adds no meaning beyond that — no routing semantics for bot, no guidance on how context affects the run — so the baseline 3 applies.

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?

States a specific verb and resource (start a Grok Bot task) plus the execution model (fire-and-forget), and names the sibling responsible for collecting output. An agent can distinguish this from get_grok_result immediately.

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?

Explicitly tells the caller to use get_grok_result later, which is a concrete usage path and de facto routing guidance. It does not contrast against ask_grok or say when a synchronous submission is preferable, so it stops short of full when/when-not coverage.

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