Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Invoice Attachments

minimax_list_attachments
Read-onlyIdempotent

List attachments for issued or received invoices, including generated PDFs, e-invoice XML, and scanned originals, with optional base64 file data.

Instructions

List the files attached to an issued or received invoice (the generated PDF, e-invoice XML, scanned originals).

Returns: str: JSON array of {AttachmentId, AttachmentFileName, AttachmentMimeType, AttachmentDate[, AttachmentData]}.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description's main addition is a Returns block describing the JSON array shape, but an output schema exists and this largely restates it. It omits genuinely useful behavior such as pagination, size implications when base64 data is included, and permission requirements.

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?

Purpose is front-loaded in a single clear sentence, and the trailing Returns block is compact. The Returns block is somewhat duplicative of the output schema, but nothing is padded or rambling.

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?

Safety is covered by annotations and return shape by the output schema, and the resource types are stated. Still, for a tool needing a record_id and an organisation context, the description gives no guidance on obtaining those identifiers or on the cost of requesting file data, leaving meaningful gaps.

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

Parameters2/5

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

Schema description coverage is reported at 0%, so the description should carry parameter meaning, yet it never mentions resource, record_id, organisation_id, or include_file_data. The only indirect hint is the 'issued or received' phrasing mapping loosely to the resource enum; the base64 file-data flag and the default-organisation behavior are left entirely to the schema.

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?

The description uses a specific verb and resource ('List the files attached to an issued or received invoice') and enumerates the attachment kinds (PDF, e-invoice XML, scanned originals), which separates it from siblings like minimax_list_issued_invoices or minimax_get_record. It stops short of naming any alternative tool, so the differentiation is implicit rather than explicit.

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 / when-not-to-use guidance and no mention of alternatives for fetching the invoice itself versus its attachments. The only context offered is the assumption that an invoice already exists ('issued or received'), with no hint about where record_id comes from.

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