Skip to main content
Glama
merterbak

Grok MCP

by merterbak
OverviewSchemaRelated ServersScoreDiscussions
Python

chat

Send a text prompt to a Grok model and receive its reply. Supports conversation history, system instructions, and multi-agent research.

Instructions

Send a text prompt to a Grok model and return its reply.

Replays prior turns from `chats/{session}.json` when a session is given,
then appends the new user message and saves the round trip.

Args:
    prompt: User message to send to the model.
    session: Optional session name. Loads and appends history to `chats/{session}.json`.
    model: Grok model id (default `grok-4.3`).
    system_prompt: Optional system instruction prepended to the conversation.
    agent_count: 4 or 16. Only valid with `grok-4.20-multi-agent` for multi-agent research.
    show_usage: Append a token usage and cost footer to the reply (default False).

Returns:
    The assistant's reply text, plus a token usage and cost footer when `show_usage` is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNogrok-4.3
promptYes
sessionNo
show_usageNo
agent_countNo
system_promptNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / show_usage
      Added value: +{
+  "default": false,
+  "title": "Show Usage",
+  "type": "boolean"
+}
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Changed1 schema field changed
    • addedInput schema / properties / agent_count
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Agent Count"
+}
  7. Added
  8. Removed
  9. Changed1 schema field changed
    • changedInput schema / properties / model / default
      Previous value: -"grok-4"New value: +"grok-4-1-fast-reasoning"
  10. Changed2 schema fields changed
    • addedInput schema / properties / session
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Session"
+}
    • removedInput schema / properties / store_messages
      Removed value: -{
-  "default": false,
-  "title": "Store Messages",
-  "type": "boolean"
-}
  11. Changed11 schema fields changed
    • removedInput schema / properties / frequency_penalty
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Frequency Penalty"
-}
    • removedInput schema / properties / max_tokens
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Max Tokens"
-}
    • changedInput schema / properties / model / default
      Previous value: -"grok-4-1-fast-non-reasoning"New value: +"grok-4"
    • removedInput schema / properties / presence_penalty
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Presence Penalty"
-}
    • removedInput schema / properties / reasoning_effort
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Reasoning Effort"
-}
    • removedInput schema / properties / stop
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Stop"
-}
    • addedInput schema / properties / store_messages
      Added value: +{
+  "default": false,
+  "title": "Store Messages",
+  "type": "boolean"
+}
    • removedInput schema / properties / temperature
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Temperature"
-}
    • removedInput schema / properties / top_p
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Top P"
-}
    • removedInput schema / properties / use_conversation_history
      Removed value: -{
-  "default": false,
-  "title": "Use Conversation History",
-  "type": "boolean"
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "chatOutput",
-  "type": "object"
-}New value: +null
  12. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / model / default
      Previous value: -"grok-4-fast"New value: +"grok-4-1-fast-non-reasoning"
    • addedInput schema / title
      Added value: +"chatArguments"
  13. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses the tool's behavior: sending a prompt, replaying prior turns from a session file, appending new messages, and saving the conversation. It also notes constraints like agent_count only valid with a specific model. Minor omission: does not mention that session files are created or modified, but 'saves the round trip' implies persistence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose, followed by structured Arg and Returns sections. It is concise for the complexity but could be slightly tighter. Every sentence adds value, though the explanation of session behavior could be integrated more succinctly.

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?

Given 6 parameters, no output schema, and no enums, the description covers all parameters, return value, and session mechanics. It lacks details on error handling, rate limits, or usage bounds, but the level of detail is adequate for an AI agent to use the tool effectively.

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

Parameters5/5

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

Schema coverage is 0%, so the description compensates fully with a detailed Args section explaining each parameter, including default values, allowed values, and constraints (e.g., agent_count only valid with grok-4.20-multi-agent). This adds significant meaning beyond the raw 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 clearly states 'Send a text prompt to a Grok model and return its reply', specifying the verb and resource. It elaborates on session replay and saving, making the tool's purpose distinct from siblings like chat_with_files or chat_with_vision.

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

Usage Guidelines3/5

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

The description implies usage for text-only chat with optional session persistence but does not explicitly guide when to use this tool versus alternatives (e.g., chat_with_files for file-based queries). No when-not-to-use or alternative names are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/merterbak/Grok-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server