Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Order / Delivery Note PDF

minimax_get_record_pdf
Read-onlyIdempotent

Render an order or stock entry delivery note as a PDF, returning attachment filename and MIME type; optionally include base64 data. For issued invoices, use generatepdf action instead.

Instructions

Render an order, or a stock entry's delivery note, as PDF. For issued invoices use minimax_run_action with action 'generatepdf' instead.

Returns: str: JSON with the attachment's file name and MIME type; the base64 data only when include_file_data is true.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real behavioral nuance beyond that: the payload only carries base64 data conditionally, which matters for cost/size decisions. The 'Returns' block is partly redundant given an output schema exists, which keeps this below a 5.

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?

Three short, front-loaded sentences: purpose, routing exclusion, return shape. No filler, though the 'Returns' paragraph restates what the output schema already declares and could be trimmed to just the conditional base64 note.

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 simple read-only render tool with an output schema and strong annotations, the description covers purpose, routing, and the one non-obvious payload behavior. Nothing critical to correct invocation is missing, though the default-organisation fallback lives only in the schema.

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 description ties the resource choice to a concrete output ('order PDF' vs 'delivery note PDF') and explains the conditional effect of include_file_data on the response payload, adding meaning beyond the field labels. Organisation id and record id semantics are left to the schema, which does document them inline.

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 pair — 'Render an order, or a stock entry's delivery note, as PDF' — and immediately scopes out the adjacent case (issued invoices) that would otherwise be ambiguous. An agent can distinguish this from minimax_run_action and minimax_list_attachments without opening a schema.

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?

Gives both the positive use case (order or stock-entry delivery note rendering) and an explicit exclusion with the named alternative and even the required argument value ('minimax_run_action with action generatepdf'). This is the routing information an agent needs and nothing is left to inference.

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