Skip to main content
Glama

APEX Runner Crypto Signals

check_trade_safety

$0.014 — Call this before opening a leveraged position so you don't walk into a crowded trade or a liquidation cascade — scores one proposed trade (coin, long/short, size_usd) 0-100 for safety from Hyperliquid top-wallet crowding, funding, nearby liquidation clusters and size impact, and returns LOW_RISK, CAUTION or DANGER with the reasoning per factor. Params: coin=ETH, side=long, size_usd=5000

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": {
      "coin": "<coin>",
      "side": "<side>",
      "size_usd": "<size_usd>"
    },
    "name": "check_trade_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesAsset to trade: BTC, ETH or SOL
sideYesPosition side you intend to open: long or short
size_usdYesPosition notional in USD, 10-10000000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.014), the 0-100 score, the three tier outcomes, and that reasoning is returned per factor. It omits latency, rate limits, or whether the result is advisory-only, but the core behavior is transparent.

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?

Front-loads the price and the call trigger, then the scoring behavior and factors in one dense sentence, followed by a compact param example. No filler, though the long single sentence packs a lot and the pricing prefix is slightly unusual as a lead.

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?

No output schema exists, and the description compensates by describing the return (0-100 score, tier label, per-factor reasoning). It doesn't state the score thresholds that map to each tier or edge-case behavior, a minor remaining gap for a 3-param tool.

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%, so the schema already documents coin, side, and size_usd with enums and bounds. The description only echoes them with an example (coin=ETH, side=long, size_usd=5000), adding little meaning beyond the structured fields, so baseline 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?

States a specific verb (scores) and resource (one proposed trade), enumerates the exact factors (Hyperliquid top-wallet crowding, funding, liquidation clusters, size impact) and the output tiers (LOW_RISK/CAUTION/DANGER). This lets an agent distinguish it from siblings like crowded_trade_detector 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?

Gives an explicit trigger: 'Call this before opening a leveraged position so you don't walk into a crowded trade or a liquidation cascade.' Clear when-to-use context, but no explicit exclusions or named alternative tools for overlapping checks.

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