Aster Finance MCP Server

getAdlQuantile

Calculate position ADL quantile estimation to assess liquidation risk for cryptocurrency trading positions on the Aster exchange.

Instructions

Get Position ADL Quantile Estimation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getAdlQuantile"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No

Implementation Reference

src/index.ts:681-682 (handler)
Executes the getAdlQuantile tool by dispatching a signed GET request to the Binance Futures API endpoint '/fapi/v1/adlQuantile'.
```
case 'getAdlQuantile':
    return makeRequest('GET', '/fapi/v1/adlQuantile', args, true);
```
src/index.ts:503-508 (schema)
Defines the input schema for the getAdlQuantile tool, which expects an object with a 'symbol' property of type string.
```
inputSchema: {
  type: 'object',
  properties: {
    symbol: { type: 'string' },
  },
},
```

src/index.ts:500-509 (registration)

Registers the getAdlQuantile tool in the list of available tools, including its name, description, and input schema.

{
  name: 'getAdlQuantile',
  description: 'Get Position ADL Quantile Estimation.',
  inputSchema: {
    type: 'object',
    properties: {
      symbol: { type: 'string' },
    },
  },
},

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 22, 2025

TDQS

D1.5/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers no information on traits like read-only status, side effects, authentication needs, rate limits, or error handling. It merely states the action without any operational context, failing to compensate for the lack of structured annotations.

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 description is a single, concise sentence, which is appropriately sized for its minimal content. However, it is under-specified rather than efficiently informative, as it lacks necessary details, making it front-loaded but insufficient rather than wastefully verbose.

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

Completeness1/5

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

Given the tool's complexity (inferred from financial context), lack of annotations, 0% schema coverage, and no output schema, the description is severely incomplete. It fails to provide essential details on purpose, usage, parameters, or behavior, making it inadequate for effective tool invocation.

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

Parameters1/5

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

The input schema has 0% description coverage, with one parameter 'symbol' undocumented in both schema and description. The description adds no meaning beyond the schema, such as explaining what 'symbol' represents (e.g., a trading pair) or its format, leaving the parameter semantics entirely unclear.

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

Purpose2/5

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

The description 'Get Position ADL Quantile Estimation' restates the tool name with minimal elaboration, making it a tautology. It specifies a verb ('Get') and resource ('Position ADL Quantile Estimation'), but lacks clarity on what ADL stands for or what the estimation entails, failing to distinguish it meaningfully from siblings like getPositionInfo or getForceOrders.

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

Usage Guidelines1/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. The description does not mention context, prerequisites, or exclusions, leaving the agent with no indication of its appropriate application relative to sibling tools such as getPositionInfo or getForceOrders.

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