LiquidVision — Crypto Derivatives Data

scan_rule

Read-onlyIdempotent

[measured] One rule tested on up to 100 coins in a single call: on which coins it was true in our hourly archive, what price did over the next 24 h and 72 h per coin (share up, median, worst, best) next to each coin's base rate, the POOLED outcome across coins with the number of distinct days behind it (coins move together, so days, not episodes, are the sample), and true_now: the coins the rule is true on right now. Use it to find where a setup has occurred and where it is live, instead of calling test_rule per coin. Frequencies from our archive, NOT a forecast; the note explains why the best of many scans is not an edge. Priced: $1.00 per call (x402, USDC on Base or Arbitrum), 200 prepaid credits (one $1 pack), or a Pro/Bot key. Takes 10-40 s on a cold cache.

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": {
      "rules": "<rules>"
    },
    "name": "scan_rule"
  }
}

Input Schema

Name	Required	Description
`coins`	No	How many coins to scan, the largest by open interest first (5-100).
`rules`	Yes	Up to 3 rules joined by commas or 'and', each metric>threshold or metric<threshold. Metrics: price_chg_1h_pct, price_chg_24h_pct, oi_chg_1h_pct, oi_chg_24h_pct, funding_apr_pct, long_pct, liq_1h_usd, liq_24h_usd. Example: funding_apr_pct>40,oi_chg_24h_pct>5
`api_key`	No	LiquidVision API key (lv_...). Omit when the key is sent as the X-API-Key header on the connection.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare read-only/idempotent safety; the description adds substantive behavior they cannot: $1.00 per call via x402 or prepaid credits, 200-credit pack, Pro/Bot key path, and 10-40 s on a cold cache. It also flags the statistical caveat that frequencies are archive data, not a forecast, and that the best of many scans is not an edge.

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?

Effectively one long sentence plus two short ones, front-loaded with the core action before pricing and latency. Dense but nearly every clause carries information an agent needs; the '[measured]' tag and parenthetical asides add minor clutter.

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, yet the description explains the return shape (per-coin truth, forward moves, base rate, pooled stats with day count, true_now), which is what an agent needs to interpret results. Cost, auth paths and latency complete the picture for a slow, paid, open-world 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% and already documents the coins range/ordering, the rule grammar and metrics, and the api_key header option, so the description is not required to carry parameter meaning. Its 'up to 100 coins' restates the upper bound, though it omits the schema's 5-coin floor, and the pooled-by-distinct-days point concerns output interpretation rather than inputs.

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?

Opens with a specific verb, resource and scope: one rule tested across up to 100 coins in a single call. It enumerates what comes back (per-coin truth, 24h/72h forward moves, pooled outcome, true_now) and names the sibling it replaces, so an agent can distinguish it from test_rule without opening either 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?

'Use it to find where a setup has occurred and where it is live, instead of calling test_rule per coin' gives an explicit alternative and the condition that selects it. The reverse case (a single coin should go to test_rule) is only implied rather than stated.

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

All LiquidVision — Crypto Derivatives Data tools Inspect

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

Need Help?