Skip to main content
Glama

Liquidity magnets and pull

get_liquidity_heatmap
Read-only

OwlChart consensus direction for a coin (one answer shared by every OwlChart chart, in the field consensus.headline) plus where leveraged positions would be liquidated around the current price: the nearest liquidity magnet above and below, the net pull direction, whale bids and asks within 5 percent, open interest by venue, long/short split, RSI and the TBO trend, with the model's measured hit rate. Crypto coins only (BTC, ETH, SOL, WLFI ...).

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>"
    },
    "name": "get_liquidity_heatmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker, e.g. BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful traits beyond that: the consensus answer is shared across every OwlChart chart and is exposed at consensus.headline, and the model's measured hit rate is reported. It still says nothing about data freshness, latency, or failure behavior for an external-data call.

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

Conciseness3/5

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

The core purpose is front-loaded in the first clause, which is good, but the rest is a single run-on sentence enumerating roughly ten outputs separated by commas, which is hard to scan. Given the absence of an output schema the enumeration is largely justified, but it could be restructured into a short lead plus a compact list.

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?

With one simple parameter and no output schema, the description carries the return-value burden and does so by naming the specific fields an agent will get, including the consensus.headline path. What remains thin is the shape and units of derived values like 'net pull direction' and the 5 percent whale band. Overall it is adequate for this tool's complexity.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description does add coin examples beyond the schema's 'BTC' (ETH, SOL, WLFI) and restricts the domain to crypto, which is a small but real increment. No ticker-format edge cases (case sensitivity, wrapped tokens) are addressed.

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 concrete composite resource: OwlChart consensus direction plus liquidation magnets, net pull, whale bids/asks, open interest by venue, long/short split, RSI and TBO trend. That is far more specific than the title and lets an agent tell it apart from narrower siblings like get_liquidations or get_open_interest. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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?

Usage is only implied by the data it bundles; there is no statement of when to prefer this over get_liquidity, get_liquidations, or get_open_interest. The one explicit constraint, 'Crypto coins only (BTC, ETH, SOL, WLFI ...)', is a scope limit rather than when-to-use guidance. An agent can infer applicability but must guess at alternatives.

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