Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

indexPriceKlines

Retrieve candlestick chart data for cryptocurrency index prices to analyze market trends and price movements over specified time periods.

Instructions

Kline/candlestick bars for the index price of a pair.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNoEnd time in ms
intervalYesKline interval
limitNoNumber of results. Default 500, max 1500.
pairYesTrading pair, e.g., BTCUSDT
startTimeNoStart time in ms

Implementation Reference

  • src/index.ts:599-600 (handler)
    Handler for the 'indexPriceKlines' tool. Dispatches a GET request to the '/fapi/v1/indexPriceKlines' endpoint using the shared makeRequest function with tool arguments.
    case 'indexPriceKlines':
    return makeRequest('GET', '/fapi/v1/indexPriceKlines', args);
  • src/index.ts:122-136 (registration)
    Tool registration in the MCP ListTools response, defining name, description, and input schema for 'indexPriceKlines'.
    {
  name: 'indexPriceKlines',
  description: 'Kline/candlestick bars for the index price of a pair.',
  inputSchema: {
    type: 'object',
    properties: {
      pair: { type: 'string', description: 'Trading pair, e.g., BTCUSDT' },
      interval: { type: 'string', description: 'Kline interval' },
      startTime: { type: 'number', description: 'Start time in ms' },
      endTime: { type: 'number', description: 'End time in ms' },
      limit: { type: 'number', description: 'Number of results. Default 500, max 1500.' },
    },
    required: ['pair', 'interval'],
  },
},
  • src/index.ts:125-135 (schema)
    Input schema for validating arguments to the 'indexPriceKlines' tool.
    inputSchema: {
  type: 'object',
  properties: {
    pair: { type: 'string', description: 'Trading pair, e.g., BTCUSDT' },
    interval: { type: 'string', description: 'Kline interval' },
    startTime: { type: 'number', description: 'Start time in ms' },
    endTime: { type: 'number', description: 'End time in ms' },
    limit: { type: 'number', description: 'Number of results. Default 500, max 1500.' },
  },
  required: ['pair', 'interval'],
},

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 mentions the data type (kline/candlestick bars) but lacks critical behavioral details: it doesn't specify if this is a read-only operation, the format/units of returned data, pagination behavior (limit parameter hints at this but not explicitly), rate limits, authentication needs, or error conditions. The description is minimal and misses key operational context.

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 that front-loads the core purpose ('Kline/candlestick bars for the index price of a pair'). There is zero wasted text, making it highly concise and well-structured for quick understanding.

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 no annotations, no output schema, and 5 parameters (though well-described in schema), the description is incomplete. It lacks behavioral transparency (e.g., read-only status, data format), usage guidelines versus siblings, and output details. For a data retrieval tool with multiple similar alternatives, this leaves significant gaps for an AI agent.

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?

Schema description coverage is 100%, so the schema fully documents all 5 parameters (pair, interval, startTime, endTime, limit) with descriptions. The description adds no additional parameter semantics beyond implying 'index price' context for the pair. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the tool retrieves 'Kline/candlestick bars for the index price of a pair,' specifying the verb (retrieves/gets) and resource (index price klines). It distinguishes from sibling 'klines' (likely spot price) and 'markPriceKlines' by specifying 'index price,' but doesn't explicitly contrast with these siblings in the description text.

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 like 'klines' or 'markPriceKlines.' The description implies it's for index price data, but doesn't state when index price is preferred over spot or mark price, or mention any prerequisites or exclusions.

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