Skip to main content
Glama

APEX Runner Crypto Signals

btc_price_tick

$0.007 — Ultra-minimal price tick at $0.01 — BTC/ETH/SOL/AVAX prices from Hyperliquid in minimal JSON. Designed for high-frequency bots that need sub-second parsing. Keys: b=BTC, e=ETH, s=SOL, a=AVAX, t=timestamp.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "btc_price_tick"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and mostly delivers: it discloses the data source (Hyperliquid), the output encoding (minimal JSON), the key abbreviations (b/e/s/a/t), and the intent for sub-second parsing. It omits freshness/update cadence, error behavior, and rate limits, and the leading "$0.007" token is unexplained.

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?

Very compact and front-loaded with the asset scope and the key mapping, both of which earn their place. The opening price fragments "$0.007" and "$0.01" are ambiguous and slightly duplicative, which costs a point.

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?

For a zero-parameter, no-annotation, no-output-schema tool, the description supplies the essential return-value contract via the key legend, which is exactly the missing piece. Only the data freshness guarantee is notably absent.

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 takes zero parameters, so the baseline is 4; the description does not need to explain inputs and correctly focuses on output keys instead.

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 names a specific resource (BTC/ETH/SOL/AVAX prices from Hyperliquid) and a specific shape (ultra-minimal price tick), which is enough to distinguish it from richer siblings like market_tick or apex_pulse. It stops short of explicitly naming which sibling to use instead when full market data is needed.

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

Usage Guidelines3/5

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

"Designed for high-frequency bots that need sub-second parsing" implies the usage context (latency-sensitive polling), which is useful, but there is no explicit when-not guidance or named alternative for agents that need broader market data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources