Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Organisations

minimax_list_organisations
Read-onlyIdempotent

Lists the organisations a user can access and returns their IDs so you can select an organisation_id required by other accounting tools.

Instructions

List the organisations (companies) the API user has access to. Every other tool needs one of these IDs as organisation_id.

Returns: str: JSON SearchResult {Rows: [{Organisation: {ID, Name}, APIAccess, MobileAccess}], TotalRows, CurrentPageNumber, PageSize, has_more}.

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

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, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description's real contribution is the cross-tool dependency on organisation_id, which is genuinely useful context; beyond that it adds nothing about permissions, rate limits, or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and prerequisite statements are front-loaded and efficient. However, the multi-line 'Returns' block restates the output schema, which already exists, so part of the definition does not earn its place.

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 prerequisite list tool, the definition covers the purpose, the downstream dependency, and the returned shape; since an output schema exists, the return details are not strictly needed. Filling in the parameter and paging story would make it fully complete.

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 as 0%, so the description carries the burden of explaining parameters, yet it says nothing about page, page_size, order, sort_field, or search_string. All meaning for the request parameters must be recovered from the nested schema alone, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ('List the organisations (companies)') and adds a scope qualifier, 'the API user has access to', which implicitly distinguishes it from the 'list_all_organisations' sibling without naming it. An agent can identify what it returns, though the contrast with the sibling remains inferential.

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?

'Every other tool needs one of these IDs as organisation_id' is strong prerequisite guidance that tells an agent this is a required entry point before other calls. It stops short of explicit when-not-to-use or naming an alternative, which keeps it below a 5.

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