Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Current Minimax User

minimax_get_current_user
Read-onlyIdempotent

Retrieves the profile of the Minimax user currently logged in, returning JSON user details or an error message.

Instructions

Return the profile of the Minimax user this server is logged in as.

Returns: str: JSON user profile, or an "Error: ..." string.

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": {
      "params": "<params>"
    },
    "name": "minimax_get_current_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the failure mode — an "Error: ..." string sentinel instead of structured data — which is genuinely useful for parsing behavior beyond the annotations.

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?

Two lines: purpose first, return contract second, zero filler. The trailing newline and the "Returns:" block are slightly verbose given a separate output schema exists, but nothing redundant is stated.

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 parameterless identity read whose annotations and output schema are both present, this is nearly complete. Only the practical detail of what happens on missing or expired credentials (error case) is partially covered by the "Error: ..." note.

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?

The schema takes only an empty, parameterless wrapper, so there is nothing semantic for the description to add; a 4 baseline for a zero-parameter tool is appropriate. The description correctly implies no identifiers are needed and that the target is fixed to the server's own credentials.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: "Return the profile of the Minimax user this server is logged in as." It clearly distinguishes itself from organisational lookups like minimax_get_organisation by scoping to the authenticated user, though it never names a sibling explicitly and gives no implicit hint that this is the identity behind other Minimax calls.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — nothing says to call this instead of minimax_get_record or minimax_list_organisations when you need the current identity, and no preconditions or exclusions are stated. The phrase "this server is logged in as" merely describes the target, not the situation that should trigger a call.

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