Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

waiaas_hl_get_spot_markets

Retrieve Hyperliquid spot market data including trading pairs and token information for crypto trading analysis.

Instructions

Get Hyperliquid spot market list (trading pairs, token info).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools/hyperliquid.ts:132-140 (handler)
    The implementation of the waiaas_hl_get_spot_markets tool, which queries the Hyperliquid API for spot markets.
    server.tool(
  'waiaas_hl_get_spot_markets',
  'Get Hyperliquid spot market list (trading pairs, token info).',
  {},
  async () => {
    const result = await apiClient.get('/v1/hyperliquid/spot/markets');
    return toToolResult(result);
  },
);

Tool Definition Quality

A3.5/5.0
Behavior3/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 partially compensates by specifying the content domain (trading pairs, token info), but lacks details on rate limits, caching behavior, authentication requirements, or pagination that would be necessary for a complete behavioral profile.

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. Information is front-loaded with the action verb, followed by the specific domain and clarifying details in parentheses.

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

Completeness4/5

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

Given the tool's simplicity (zero parameters, no output schema, no annotations), the description adequately covers the functional scope. It successfully communicates what the tool retrieves, which is sufficient for this complexity level, though it could benefit from mentioning data freshness or scope limitations.

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 input schema contains zero parameters, establishing a baseline score of 4 per the evaluation rubric. The description appropriately makes no mention of parameters since none exist.

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 uses a specific verb ('Get') and clearly identifies the resource ('Hyperliquid spot market list'). The parenthetical clarification '(trading pairs, token info)' adds specificity about the data returned. It implicitly distinguishes from siblings like waiaas_hl_get_markets by specifying 'spot' and from Polymarket tools via 'Hyperliquid', though explicit differentiation would strengthen it further.

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 such as waiaas_hl_get_markets (likely perpetuals) or waiaas_pm_get_markets. There are no conditions, prerequisites, or explicit comparisons to sibling tools listed.

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/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server