grok-build-mcp

grok_chat

Send a one-shot prompt to xAI Grok and receive its reply. Designed for stateless, single-turn queries.

Instructions

Send a one-shot prompt to xAI Grok and return its reply. Stateless — for multi-turn use grok_consult.

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": {
      "prompt": "<prompt>"
    },
    "name": "grok_chat"
  }
}

Input Schema

Name	Required	Description
`prompt`	Yes	The prompt to send to Grok.
`model`	No	Override default Grok model (e.g. 'grok-4').
`timeout`	No	Per-call timeout in seconds. Defaults to 300. Raise for long grok-4 reasoning.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Jun 12, 2026

addedInput schema / properties / timeout

Added value: +{
+  "description": "Per-call timeout in seconds. Defaults to 300. Raise for long grok-4 reasoning.",
+  "exclusiveMinimum": true,
+  "minimum": 0,
+  "type": "number"
+}

First observedv0.1.0May 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations provided, but the description fully covers behavioral traits: stateless, one-shot, returns reply. No contradictions; the description is sufficient for understanding the tool's 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 concise sentences with no waste. Every part is necessary and informative, front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple stateless nature, 3 parameters, and no output schema, the description covers all needed context: purpose, statelessness, usage guidance, and parameter details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by explaining model parameter overrides and timeout details ('Defaults to 300. Raise for long grok-4 reasoning'), going beyond the schema.

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 explicitly states 'Send a one-shot prompt to xAI Grok and return its reply', clearly identifying the action and resource. It distinguishes from sibling tools by noting 'Stateless — for multi-turn use grok_consult'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance: use for one-shot stateless queries, and directs to grok_consult for multi-turn interactions, naming the specific alternative.

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

Deploy Server