htx-mcp

HTX Get Instrument Rules

htx_get_instrument_rules

Read-onlyIdempotent

Retrieve HTX instrument rules for spot or swap products, including precision, minimums, and status, before placing orders.

Instructions

Return HTX precision, minimum, status, and contract rules for one product.

Use these rules before constructing any quantity or price.

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": {
      "product": "<product>"
    },
    "name": "htx_get_instrument_rules"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	HTX product family: spot or USDT-margined perpetual swap.
`instrument`	No	Optional exact symbol or contract; omit to list all rules.

Output Schema

Name	Required	Description	Default
`rules`	Yes
`matched`	Yes
`product`	Yes
`instrument`	Yes
`available_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.3Sep 8, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description has a lower burden. It adds no behavioral traits beyond stating the return content; it also does not contradict the annotations.

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 two short sentences with no filler. It front-loads the purpose and then gives a brief usage directive, making it easy for an agent to scan and act on quickly.

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 simple read-only lookup tool with an output schema, detailed input schema, and strong annotations, the description is sufficient. It states what is returned and when to use it; the schema covers the optional instrument and product families.

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?

Input schema coverage is 100% and parameter descriptions are already detailed, including the product enum and instrument optionality. The description adds no meaningful parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Return HTX precision, minimum, status, and contract rules for one product.' This clearly distinguishes it from sibling market/account/risk tools and states the exact kind of data the agent will receive.

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?

The description explicitly advises when to use the tool: 'Use these rules before constructing any quantity or price.' It does not enumerate alternatives or when-not-to-use cases, but the usage context is clear and actionable.

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

Deploy Server