Skip to main content
Glama

get_derivatives

Derivatives data for a symbol on OKX: open interest, long/short ratio, funding, CVD, taker volume, 1 h candles, put/call and a composite sentiment score (0–100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_derivatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSymbol, e.g. BTC (default) or ETH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the disclosure burden. It usefully names the data source (OKX) and the scale of the sentiment score (0–100), which is real behavioral context. However, it says nothing about data freshness/update cadence, rate limits, or whether missing symbols return errors or defaults – all material for a live market-data tool.

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?

One sentence, resource and scope front-loaded, every clause enumerating a distinct returned datum. There is no filler and no repetition of the name.

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 single optional parameter read tool with no output schema, the enumeration of returned data fields effectively substitutes for a return description. Remaining gaps are the update cadence and what happens with unsupported symbols, which are minor against this tool's simplicity.

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%: the single symbol parameter is fully documented in the schema, including the BTC default and an ETH example. The description's 'for a symbol' adds nothing beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (derivatives data for a symbol) and enumerates exactly what is bundled: open interest, long/short ratio, funding, CVD, taker volume, candles, put/call, sentiment score. This is far more precise than the bare name. It does not differentiate from the nearest sibling (get_market / get_metrics), which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative named. The content list implies the tool is for derivatives/sentiment analysis, but an agent must infer that it should be chosen over get_market or get_metrics for positioning data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources