SiteCheck Crypto & Finance

HTX 24h ticker for one market: open, high, low, close

finance_huobi_tickers

Read-only

HTX (formerly Huobi) 24h ticker for one market (e.g. btcusdt): open, high, low, close, bid/ask, base and quote volume and trade count, from HTX's public market tickers endpoint. Related tools on this server, for a different need: finance_bitget_tickers when you need Bitget spot ticker for one pair: last price, bid/ask, 24h; finance_bitstamp_tickers when you need Bitstamp spot ticker for one pair: last, bid, ask, 24h. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "finance_huobi_tickers"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	HTX market in lowercase, e.g. btcusdt, ethusdt

Output Schema

Name	Required	Description	Default
`ask`	No
`bid`	No
`low`	No
`high`	No
`open`	No
`close`	No
`source`	No
`symbol`	No
`checkedAt`	No
`trades24h`	No
`baseVolume24h`	No
`quoteVolume24h`	No
`changePercent24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a read-only, open-world operation. The description adds useful behavioral context beyond annotations: the data comes from HTX's public market tickers endpoint, each successful call costs $0.002 USDC via x402, and failed calls are not charged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and return fields, followed by alternative-tool guidance and pricing. It is slightly verbose in restating the Bitget and Bitstamp alternatives, but every part is useful for selection or cost awareness.

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

Completeness5/5

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

For a single-parameter ticker tool with an output schema and read-only annotations, the description covers the endpoint, exchange scope, returned fields, alternatives, and billing behavior. Nothing material is missing for correct selection and invocation.

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 coverage is 100%, and the schema already documents that symbol must be a lowercase HTX market such as btcusdt. The description reinforces that this is for one market but does not add substantial meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and operation: an HTX (formerly Huobi) 24h ticker for one market. It enumerates the returned fields and explicitly distinguishes this tool from Bitget and Bitstamp ticker siblings, so an agent can identify its scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context by naming finance_bitget_tickers and finance_bitstamp_tickers as alternatives for different exchanges. It does not explicitly address other ticker siblings such as Binance or MEXC, but the exchange-specific framing makes the intended use clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?