Skip to main content
Glama
Sign In
my-minimax-mcp

my-minimax-mcp

by wongo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

minimax_chat

Conduct multi-turn conversations with MiniMax AI. Preserve context across calls to offload coding tasks and reduce token usage.

Instructions

Multi-turn chat with MiniMax AI. Supports conversation context preservation across multiple calls.

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": {
      "message": "<message>"
    },
    "name": "minimax_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage to send to MiniMax
conversationIdNoID of existing conversation to continue
modelNoModel override (default: MINIMAX_DEFAULT_MODEL env var, typically M2.7)
systemPromptNoSystem prompt (only for new conversations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "MiniMax-M2.5",
-  "MiniMax-M2.7",
-  "MiniMax-M2.5-highspeed",
-  "MiniMax-M2.7-highspeed"
-]New value: +[
+  "MiniMax-M3",
+  "MiniMax-M2.5",
+  "MiniMax-M2.7",
+  "MiniMax-M2.5-highspeed",
+  "MiniMax-M2.7-highspeed"
+]
  2. First observedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses multi-turn capability and context preservation, but lacks details on auth, rate limits, or any side effects.

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 a single, concise sentence that efficiently conveys the tool's purpose and key feature without redundancy.

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

Completeness3/5

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

For a simple 4-parameter chat tool with no output schema, the description covers the core functionality but does not explain return format, error handling, or advanced usage scenarios.

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 schema already documents all parameters. The description adds minimal extra meaning beyond the schema descriptions.

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 the tool is for multi-turn chat with MiniMax AI and emphasizes conversation context preservation, which distinguishes it from sibling tools like minimax_agent_task or minimax_generate_code.

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 chat with context preservation but does not explicitly contrast with alternative tools or state when not to use it.

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

Deploy Server

Other Tools