Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Payroll Setting

minimax_get_payroll_settings
Read-onlyIdempotent

Retrieves a statutory payroll setting by code, such as minimum wage or contribution rates, and returns the value valid on a specified date. Not organization-specific.

Instructions

Return a statutory payroll setting by code (minimum wage, contribution rates, ...) valid on a date. Not organisation-specific.

Returns: str: JSON SearchResult of payroll settings.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new context: the lookup is time-sensitive ('valid on a date'), the data is statutory rather than customer-owned, and the return is a JSON SearchResult. It does not say what happens with an unknown code or how an omitted date is resolved.

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?

Front-loaded with the core scope constraint ('statutory', 'valid on a date', 'not organisation-specific') in one tight sentence, with no filler. The short Returns block is compact and clearly separated.

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 added 'Returns: str: JSON SearchResult' line is largely redundant, but everything an agent needs to select and call this single-parameter read tool (subject matter, time validity, non-org scope) is present. The only real omission is the role of the two optional scoping parameters.

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?

The description explains what 'code' means by giving example setting categories and clarifies the date semantics behind 'as_of', which adds value. However, it leaves the documented-as-absent customer_code and external_user_identifier params unexplained — especially notable since the text insists the tool is 'not organisation-specific', raising the question of why a customer code is accepted at all.

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 and resource ('Return a statutory payroll setting by code') with concrete examples of what a setting is (minimum wage, contribution rates). The 'Not organisation-specific' clause meaningfully distinguishes it from organisation-scoped settings tools, though it never names a specific sibling to steer toward.

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

Usage Guidelines3/5

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

The 'Not organisation-specific' note implies when to choose this over org-scoped lookups, but the guidance is implicit rather than stated. There is no explicit when-to-use/when-not rule and no named alternative tool.

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