Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

markPriceKlines

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

Instructions

Kline/candlestick bars for the mark price of a symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNoEnd time in ms
intervalYesKline interval
limitNoNumber of results. Default 500, max 1500.
startTimeNoStart time in ms
symbolYesTrading symbol

Implementation Reference

  • Handler for the 'markPriceKlines' tool. Executes a GET request to the '/fapi/v1/markPriceKlines' endpoint using the provided arguments.
    case 'markPriceKlines':
        return makeRequest('GET', '/fapi/v1/markPriceKlines', args);
  • Input schema definition for the 'markPriceKlines' tool, specifying required symbol and interval parameters.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string', description: 'Trading symbol' },
        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: ['symbol', 'interval'],
    },
  • src/index.ts:137-151 (registration)
    Registration of the 'markPriceKlines' tool in the list of available tools, including name, description, and input schema.
    {
      name: 'markPriceKlines',
      description: 'Kline/candlestick bars for the mark price of a symbol.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Trading symbol' },
          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: ['symbol', 'interval'],
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It doesn't disclose if this is a read-only operation, rate limits, authentication needs, or response format. The description is minimal and doesn't add meaningful context beyond the basic purpose, leaving gaps for a tool with parameters.

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 with zero waste. It's front-loaded and appropriately sized, making it easy to parse without unnecessary elaboration.

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 a tool with 5 parameters, the description is incomplete. It lacks details on behavior, return values, or usage context, making it inadequate for an agent to fully understand how to invoke and interpret results without external knowledge.

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 parameters like 'endTime' and 'interval.' The description adds no additional meaning beyond implying 'symbol' and 'interval' are key, which is already clear from the schema. 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 mark price of a symbol,' specifying the verb (retrieve) and resource (mark price klines). It distinguishes from sibling tools like 'klines' (likely regular price) and 'indexPriceKlines' by specifying 'mark price,' though it doesn't explicitly contrast them.

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 'indexPriceKlines.' The description implies it's for mark price data but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer context from sibling names alone.

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