LiquidVision — Crypto Derivatives Data

get_api_key

Get a free LiquidVision API key for this agent's owner, by email, without a browser. Works for a NEW email only (an existing account's key is never returned; its owner sees it at liquidvision.app/data). Use the key as X-API-Key on REST or on this MCP endpoint: 120 req/min instead of the shared anonymous budget, plus 100 metered calls a day (history, positions: get_funding_history, get_open_interest_history, get_funding_settlements, get_hl_whales, get_history...), and to upgrade later to Pro/Bot (10,000 / 100,000 metered calls a day, exports, webhook alerts). Ask the user for the email first; do not invent one.

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": {
      "email": "<email>"
    },
    "name": "get_api_key"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The owner's email address; the key is issued to it once.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / email / description
```
Added value: +"The owner's email address; the key is issued to it once."
```
AddedSep 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations it discloses the key's effects and limits: issued once per email, never re-returned, usable as X-API-Key on REST or this MCP endpoint, raising the caller to 120 req/min versus the shared anonymous budget with 100 metered calls a day, plus an upgrade path. This is exactly the sort of quota and one-shot-issuance context annotations cannot 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?

Purpose and the new-email constraint are front-loaded, and most clauses carry actionable information. The inline enumeration of metered tools (get_funding_history, get_hl_whales, etc.) and the Pro/Bot tier figures are partially promotional and could be trimmed without losing calling guidance.

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?

For a one-parameter, no-output-schema tool this covers nearly everything an agent needs: eligibility, provenance of the email, how to use the returned key, and rate-limit consequences. It stops short of saying explicitly that the response contains the key string and what happens on an ineligible/existing email.

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 email parameter is already documented, but the description adds real meaning: it must be a new email, the key is bound to it permanently, and the agent must solicit it from the user rather than fabricate one. It does not specify format/validation, hence not a 5.

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 states a specific verb and resource - obtain a free LiquidVision API key for the agent's owner by email - and immediately scopes it ('Works for a NEW email only'), which cleanly separates it from every data-retrieval sibling in the tool list.

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 gives explicit when-to-use direction ('Ask the user for the email first; do not invent one') and an explicit when-not case: an existing account's key is never returned and its owner must go to liquidvision.app/data. That is a genuine alternative routing instruction, not just context.

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?