Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

liquidity_levels

Read-onlyIdempotent

Detect buy-side and sell-side liquidity levels for crypto or stocks, check swept status, relative-equal pools, and nearest untaken targets by symbol and timeframe.

Instructions

[Trading Data API] ICT liquidity levels: buy-side liquidity (above swing highs) & sell-side (below swing lows), sweep/taken status, relative-equal pools, and nearest untaken targets. Crypto or stocks.

Example: /v1/liquidity-levels?symbol=TQQQ&timeframe=1h

Use when you want buy-side/sell-side liquidity levels and whether they were swept. Not for gap zones (use fvg) or actual liquidation events (use liquidations).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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": "liquidity_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. e.g. BTC, NVDA, TQQQ (or any with &class=).
lookbackNoOptional. Candles to analyze (default 300, max 500).
timeframeNoOptional. 1m..1W (default 1h).
swing_lengthNoOptional. Pivot strength — bars each side of a swing (default 5). Tune to match your chart indicator.
include_sweptNoOptional. true to include already-taken levels (default false = resting only).
equal_threshold_pctNoOptional. Group swings within this % as relative-equal pools (default 0.1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description rightly spends its words elsewhere: it discloses the pricing model (x402 USDC on Base or WICKEDAPI_API_KEY) and pre-empts the biggest agent trap by explaining that HTTP 402 with a decoded price is a quote, not a failure. That is behavior an agent cannot infer from annotations or schema.

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?

Front-loaded one-line definition, then example, then when-to-use exclusions, then behavior/payment. Every sentence carries new information and nothing is repeated from the schema.

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?

With no output schema, the description compensates by enumerating what the response contains (buy-side/sell-side levels, swept status, equal pools, nearest untaken targets) and by describing the non-200 payment path. For a six-parameter read-only data endpoint that is sufficient for correct invocation.

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?

Schema coverage is 100%, so the schema already documents symbol, lookback, timeframe, swing_length, include_swept and equal_threshold_pct; baseline would be 3. The description adds modest semantic grounding by tying 'sweep/taken status' and 'relative-equal pools' to the corresponding parameters and by showing a concrete query (`?symbol=TQQQ&timeframe=1h`), though it does not explain units or defaults for the numeric knobs.

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 names the resource (ICT buy-side liquidity above swing highs, sell-side below swing lows) and the specific data returned (sweep/taken status, relative-equal pools, nearest untaken targets). It also names the two closest siblings it is not (fvg, liquidations), so an agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

Usage is explicit: 'Use when you want buy-side/sell-side liquidity levels and whether they were swept', followed by exclusions routing to named alternatives ('Not for gap zones (use fvg) or actual liquidation events (use liquidations)'). This is the when/when-not/alternative pattern in full.

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

Deploy Server

Other Tools