Skip to main content
Glama

Ask Grok Bot

ask_grok

Sends a task to a Grok Bot webhook and waits for the completed answer. If it times out, returns a request_id so you can retrieve the result later.

Instructions

Send a task to Grok Bot and wait for the answer. Returns the answer, or a request_id with status pending if it times out so you can collect it later with get_grok_result.

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

Input Schema

NameRequiredDescriptionDefault
botNoOptional bot name to route the task to.
taskYesThe task for Grok Bot to perform.
contextNoOptional extra context for the bot.
wait_secondsNoHow long to wait for a result, in seconds. Default 300, max 780.

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 behavioral burden well. It discloses that the call blocks and waits, that it may return a pending request_id on timeout, and how to later collect the result, though it omits details such as authentication, rate limits, or error 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?

Two sentences are used efficiently, with the synchronous behavior and timeout fallback presented up front and no wasted wording.

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 four-parameter tool with no output schema and no annotations, the description explains the important return paths: a direct answer or a pending request_id. It is nearly complete, with only peripheral operational details missing.

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 the input schema already explains task, bot, context, and wait_seconds. The description adds only the timeout consequence, not additional parameter-level meaning beyond what the schema provides.

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 description uses a specific verb and resource: send a task to Grok Bot and wait for the answer. It also distinguishes the timeout path by naming get_grok_result as the follow-up tool, which helps an agent choose correctly.

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?

It clearly establishes the intended usage pattern: synchronous waiting for a result, with an explicit fallback to get_grok_result after a timeout. It does not address when to prefer a sibling like submit_grok_task, so it falls short of fully exhaustive alternative guidance.

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