Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

ping

Test connectivity to the Aster Finance Futures API to verify system availability and ensure cryptocurrency trading operations can proceed.

Instructions

Test connectivity to the Rest API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:583-584 (handler)
    The execution handler for the 'ping' tool. It dispatches a GET request to the '/fapi/v1/ping' endpoint using the shared makeRequest helper function.
    case 'ping':
  return makeRequest('GET', '/fapi/v1/ping', {});
  • src/index.ts:52-52 (registration)
    The tool registration entry in the listTools response, including name, description, and input schema (empty object).
    { name: 'ping', description: 'Test connectivity to the Rest API.', inputSchema: { type: 'object', properties: {} } },
  • src/index.ts:52-52 (schema)
    Input schema definition for the 'ping' tool: an empty object (no parameters required).
    { name: 'ping', description: 'Test connectivity to the Rest API.', inputSchema: { type: 'object', properties: {} } },

Tool Definition Quality

B3.1/5.0
Behavior2/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. It states the tool tests connectivity but doesn't describe what 'testing' entails—whether it returns a simple success/failure, latency metrics, error details, or requires authentication. This is a significant gap for a tool with zero annotation coverage.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse 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?

Given the tool's simplicity (0 params, no output schema), the description is minimal but inadequate. It doesn't explain what the test returns or how to interpret results, which is crucial for connectivity testing. With no annotations and low complexity, more detail is needed to be complete.

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 schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, but it doesn't fully compensate for other gaps, so it scores just below the maximum.

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 as testing connectivity to the Rest API, which is a specific action (test) on a resource (Rest API). However, it doesn't distinguish itself from potential sibling tools like 'time' that might also test connectivity, 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. In a context with many sibling tools, it doesn't specify if this is for initial setup, troubleshooting, or as a prerequisite for other operations, leaving the agent without clear usage context.

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