MAX Exchange MCP Server

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

With no annotations provided, the description carries the full burden. It discloses one key behavioral trait: leaving the parameter empty returns all markets ('留空回傳全部'). However, it lacks disclosure on read-only safety, rate limits for bulk queries, caching behavior, or whether the data is real-time versus delayed.

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

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

Highly efficient two-line structure using standard :param documentation format. The first line establishes purpose; the second details the parameter with example. No redundant text, properly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a single-parameter read operation with output schema available. The description covers the input parameter well but misses opportunity to clarify relationship with 'get_ticker' or warn about performance implications of fetching all markets at once. Sufficient but not comprehensive.

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

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

Excellent compensation for 0% schema coverage. The description fully documents the single 'markets' parameter: format (comma-separated), concrete example ('btcusdt,ethusdt'), type (string/null), and default behavior (empty returns all). This provides complete semantic meaning absent from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it retrieves real-time quotes ('即時行情') for multiple markets ('多個市場'), with explicit emphasis on batch querying capability ('一次查詢多個'). This effectively distinguishes it from the sibling tool 'get_ticker' (singular). Minor deduction for not specifying what data fields constitute a ticker (e.g., price, volume, change).

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

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

No explicit when-to-use guidance or comparison to alternatives. While the batch capability is mentioned ('可一次查詢多個'), there is no guidance on when to prefer this over 'get_ticker' for single queries, or warnings about querying 'all' markets (empty parameter) versus specific ones.

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