Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

fundingInfo

Retrieve funding rate configuration for cryptocurrency trading symbols to inform trading decisions and risk management strategies.

Instructions

Get funding rate config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoTrading symbol

Implementation Reference

  • Handler for the 'fundingInfo' tool that delegates to the makeRequest helper to perform a GET request to the Aster Futures API fundingInfo endpoint.
    case 'fundingInfo':
        return makeRequest('GET', '/fapi/v1/fundingInfo', args);
  • Input schema definition for the 'fundingInfo' tool, specifying an optional 'symbol' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string', description: 'Trading symbol' },
      },
    },
  • src/index.ts:175-184 (registration)
    Registration of the 'fundingInfo' tool in the tools list provided by the ListToolsRequestSchema handler.
    {
      name: 'fundingInfo',
      description: 'Get funding rate config.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Trading symbol' },
        },
      },
    },
  • Shared helper function 'makeRequest' that handles HTTP requests to the Aster API, including signing with API key and secret when required, used by the fundingInfo handler and other tools.
    const makeRequest = async (method: 'GET' | 'POST' | 'DELETE', path: string, params: any, isSigned = false) => {
      try {
        let config: any = {
          method,
          url: path,
        };
    
        if (isSigned) {
          if (!API_KEY || !API_SECRET) {
            throw new McpError(ErrorCode.InvalidRequest, 'API_KEY and API_SECRET must be configured.');
          }
          params.timestamp = Date.now();
          const queryString = new URLSearchParams(params).toString();
          const signature = crypto.createHmac('sha256', API_SECRET).update(queryString).digest('hex');
          params.signature = signature;
          
          config.headers = { 'X-MBX-APIKEY': API_KEY };
        }
        
        if (method === 'GET' || method === 'DELETE') {
          config.params = params;
        } else { // POST
          config.data = new URLSearchParams(params).toString();
          config.headers = { ...config.headers, 'Content-Type': 'application/x-www-form-urlencoded' };
        }
    
        const response = await this.axiosInstance.request(config);
        return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new McpError(
            ErrorCode.InternalError,
            `Aster API error: ${error.response?.data?.msg || error.message}`
          );
        }
        throw error;
      }
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying it's read-only, but doesn't specify permissions, rate limits, or response format. This leaves gaps for a tool that likely interacts with financial data.

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 no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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?

For a tool with no annotations and no output schema, the description is too minimal. It doesn't explain what 'funding rate config' entails (e.g., settings, thresholds) or the return format, leaving the agent with insufficient context to use it effectively in a financial trading environment.

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?

The input schema has 100% description coverage, with the 'symbol' parameter documented as 'Trading symbol'. The description doesn't add any extra meaning beyond this, such as examples or format details, so it meets the baseline for high schema coverage without compensation.

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 'Get funding rate config' clearly states the action ('Get') and resource ('funding rate config'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'fundingRate' (which likely provides current funding rates rather than configuration), leaving some ambiguity about its specific scope.

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?

The description provides no guidance on when to use this tool versus alternatives. Given sibling tools like 'fundingRate', it's unclear whether this is for retrieving configuration settings versus real-time data, and there are no prerequisites or exclusions mentioned.

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