Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

fvg

Read-onlyIdempotent

[Trading Data API] Fair Value Gap zones (standard ICT/LuxAlgo) with CE (50%), gap size, age, fill status, distance from price. Standard timeframes match TradingView candles. Crypto or stocks.

Example: /v1/fvg?symbol=BTC&timeframe=1h

Use when you want Fair Value Gap zones (ICT-style imbalances) with fill status and distance from price. Not for swing-high/low liquidity pools (use liquidity_levels).

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

Input Schema

NameRequiredDescriptionDefault
classNoOptional. stock|crypto for non-curated symbols.
symbolYesRequired. e.g. BTC, NVDA, SPY (or any with &class=).
lookbackNoOptional. Timeframe candles to analyze (default 120, max 500).
timeframeNoOptional. 1m,5m,15m,30m,1h,2h,4h,6h,12h,1D,1W (default 1h). Matches TradingView candles.
min_gap_pctNoOptional. Filter out gaps smaller than this % of price (default 0 = all).
include_filledNoOptional. true to include filled FVGs (default false = active only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description explains pricing behavior: x402 USDC on Base or free with WICKEDAPI_API_KEY, and clarifies that an HTTP 402 response is a price quote rather than a failure. It also mentions read-only behavior and that timeframes match TradingView candles, adding useful context not covered by the 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?

The description is front-loaded with the core resource and returned fields, then moves to an example, usage boundaries, and payment behavior. Every sentence contributes useful information without repetition or waste.

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?

There is no output schema, but the description enumerates the relevant return fields (CE, gap size, age, fill status, distance from price). With all parameters documented in the schema and pricing/usage behavior covered in the description, an agent has enough information to call the tool correctly.

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 description coverage is 100%, so the schema already documents all six parameters in detail. The description only provides an example using symbol and timeframe, adding little semantic information beyond what the schema already provides.

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 a specific resource (Fair Value Gap zones) and enumerates the exact data returned: CE, gap size, age, fill status, and distance from price. It also explicitly distinguishes itself from liquidity_levels, so an agent can tell what it does and what it does not do.

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?

It states when to use the tool ('when you want Fair Value Gap zones ... with fill status and distance from price') and when not to use it ('Not for swing-high/low liquidity pools'), naming the alternative sibling tool. This is explicit routing guidance with no inference required.

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

All Wicked MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources