Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

setMultiAssetsMode

Switch between Multi-Assets and Single-Asset margin modes to manage cross-margin trading across multiple cryptocurrency positions.

Instructions

Change user's Multi-Assets mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
multiAssetsMarginYes"true" for Multi-Assets Mode; "false" for Single-Asset Mode

Implementation Reference

  • src/index.ts:621-622 (handler)
    The handler logic for the 'setMultiAssetsMode' tool. It invokes the shared makeRequest function to perform a signed POST request to the '/fapi/v1/multiAssetsMargin' endpoint with the tool arguments.
    case 'setMultiAssetsMode':
    return makeRequest('POST', '/fapi/v1/multiAssetsMargin', args, true);
  • src/index.ts:228-238 (registration)
    Registration of the 'setMultiAssetsMode' tool in the list of available tools, including its description and input schema definition.
    {
  name: 'setMultiAssetsMode',
  description: "Change user's Multi-Assets mode.",
  inputSchema: {
    type: 'object',
    properties: {
      multiAssetsMargin: { type: 'string', description: '"true" for Multi-Assets Mode; "false" for Single-Asset Mode' },
    },
    required: ['multiAssetsMargin'],
  },
},
  • src/index.ts:231-237 (schema)
    Input schema for the 'setMultiAssetsMode' tool, defining the expected parameter 'multiAssetsMargin' as a string.
    inputSchema: {
  type: 'object',
  properties: {
    multiAssetsMargin: { type: 'string', description: '"true" for Multi-Assets Mode; "false" for Single-Asset Mode' },
  },
  required: ['multiAssetsMargin'],
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Change'), suggesting it's not read-only, but doesn't disclose behavioral traits like required permissions, side effects (e.g., impact on open positions), rate limits, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence ('Change user's Multi-Assets mode.') that is front-loaded and wastes no words. It's appropriately sized for the tool's simple purpose.

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

Completeness2/5

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

Given the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It doesn't explain what Multi-Assets mode is, the implications of changing it, or what the tool returns. With no output schema, the description should at least hint at the response, but it doesn't, leaving significant gaps.

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 input schema has 100% description coverage, with the parameter 'multiAssetsMargin' clearly documented as a string with values 'true' for Multi-Assets Mode and 'false' for Single-Asset Mode. The description doesn't add meaning beyond this, but with high schema coverage and only one parameter, a baseline of 4 is appropriate as the schema fully compensates.

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

Purpose3/5

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

The description 'Change user's Multi-Assets mode' clearly states the action (change) and target (user's Multi-Assets mode), but it's vague about what Multi-Assets mode entails and doesn't distinguish from sibling tools like 'getMultiAssetsMode' (which presumably reads the mode) or 'setPositionMode' (which might be related). It avoids tautology but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), context (e.g., after checking current mode with getMultiAssetsMode), or exclusions (e.g., not for single-asset accounts). The description alone offers no usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/questflowai/aster-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server