Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Describe Minimax Resource

minimax_describe_resource
Read-onlyIdempotent

Describes a resource’s supported operations, actions, listing tools, and record fields with meanings and allowed codes. Use it before creating or updating records to confirm valid inputs.

Instructions

Describe a resource without calling Minimax: which operations and actions it supports, which tool lists it, and every field of its records with meaning and allowed codes. Call this before minimax_create_record or minimax_update_record.

Returns: str: JSON {resource, label, parent, operations, actions, list_with, fields}.

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_describe_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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=false, so the safety profile is fully covered. The description adds the useful behavioral note that this is pure metadata introspection ('without calling Minimax'), but says nothing about cost, caching, or failure modes for an invalid resource key.

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?

Three short sentences, front-loaded with the action and enumeration, followed by the usage directive and a compact return shape. No redundant restatement of the name or title.

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?

An output schema exists, so the brief return line is sufficient rather than required, and the description covers purpose, contents and ordering relative to write tools. The only missing element is any description of what the single resource argument accepts, which is a minor gap given the enum.

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 reported at 0% for the single 'resource' parameter, so the description must compensate for the meaning of the argument. It never mentions the resource key at all; the only guidance comes from the 36-value enum in the schema, which is self-describing but leaves the description adding nothing about valid resource scope.

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?

States a specific verb and resource ('Describe a resource') and enumerates exactly what comes back: supported operations and actions, the listing tool, and every field with meaning and allowed codes. It also contrasts itself with the data-fetching siblings by saying 'without calling Minimax', so an agent can tell it apart from minimax_get_record.

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?

Gives an explicit directive to 'Call this before minimax_create_record or minimax_update_record', which names the alternatives and the condition that selects them. It does not cover other plausible uses (e.g. before bulk listing/filtering), but the primary routing decision is spelled out.

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