Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

long_short_ratio

Read-onlyIdempotent

Fetch Binance long/short positioning ratios—global accounts, top traders, and taker buy/sell—for a crypto symbol to assess market sentiment and crowding.

Instructions

[Trading Data API] Binance long/short ratios: global account, top-trader account, top-trader position, and taker buy/sell. Companion to funding-oi.

Example: /v1/long-short-ratio?symbol=BTC&period=1h

Use when you want Binance positioning ratios (global accounts, top traders, taker buy/sell). Not for funding or open interest (use funding_oi).

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

Input Schema

NameRequiredDescriptionDefault
periodNoOptional. One of 5m,15m,30m,1h,2h,4h,6h,12h,1d (default 5m).
symbolYesRequired. Base crypto symbol (e.g. BTC). Mapped to <SYMBOL>USDT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/safe semantics, and the description adds non-obvious context: paid via x402 or an API key, and that an HTTP 402 carries a price quote rather than being a failure. That pricing/auth disclosure is exactly the kind of behavioral info annotations can't convey.

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-loaded with the resource list, then example, usage, and behavior. The 'Use when...' sentence partially restates the opening enumeration, a minor redundancy, but overall it is tight and scannable.

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, but the description names the four ratio families returned and covers payment/auth behavior and an example call, which is sufficient for correct invocation. Return shape/pagination specifics are the only minor gap.

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% with each parameter described (symbol mapping to <SYMBOL>USDT, period enum). The description echoes usage only through the example query string and adds little parameter detail beyond the schema, 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+resource (Binance long/short ratios) and enumerates the four sub-metrics it returns, immediately distinguishing it from siblings. An agent can identify its function 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 Guidelines5/5

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

Explicitly says when to use it ('Use when you want Binance positioning ratios') and when not to ('Not for funding or open interest (use funding_oi)'), naming the alternative tool. Routing is unambiguous.

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