Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

exchangeInfo

Retrieve current trading rules and symbol details for cryptocurrency futures on the Aster exchange, enabling informed trading decisions with accurate market structure information.

Instructions

Get current exchange trading rules and symbol information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:587-588 (handler)
    Handler implementation for the 'exchangeInfo' tool. It makes an unauthenticated GET request to the '/fapi/v1/exchangeInfo' endpoint using the shared makeRequest function, which returns exchange trading rules and symbol information.
    case 'exchangeInfo':
  return makeRequest('GET', '/fapi/v1/exchangeInfo', {});
  • src/index.ts:54-54 (registration)
    Registration of the 'exchangeInfo' tool in the ListTools response. Includes the tool name, description, and input schema (empty object, no parameters required).
    { name: 'exchangeInfo', description: 'Get current exchange trading rules and symbol information.', inputSchema: { type: 'object', properties: {} } },
  • src/index.ts:54-54 (schema)
    Input schema for the 'exchangeInfo' tool, defining it as an object with no properties (no input parameters).
    { name: 'exchangeInfo', description: 'Get current exchange trading rules and symbol information.', inputSchema: { type: 'object', properties: {} } },

Tool Definition Quality

B3.2/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 the full burden of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't specify if it requires authentication, has rate limits, returns real-time or cached data, or details the response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get current exchange trading rules and symbol information') with zero wasted words. Every part of the sentence earns its place by clearly conveying the tool's function.

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

Completeness3/5

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

Given the tool has 0 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on behavioral aspects (e.g., authentication needs, data format) that would be helpful for an agent, especially without annotations. This makes it complete enough for basic use but with clear 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 tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description doesn't add any parameter information, which is appropriate here, but it doesn't explicitly state 'no parameters required,' so it doesn't achieve a perfect score.

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's purpose with a specific verb ('Get') and resource ('current exchange trading rules and symbol information'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'getAccountInfo' or 'getBalance', which could also provide informational data, so it doesn't reach the highest score.

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. With many sibling tools available (e.g., 'getAccountInfo', 'getBalance'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on the name 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