Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

Intraday open interest and funding

oi_funding_history
Read-onlyIdempotent

The intraday path of open interest and funding for one pair, aggregated across venues, oldest first. Use it for "how has BTC open interest moved today", "was funding rising into that move", "show me the OI path over the last 12 hours". Keyless: the free pairs, the last 24h at 1-hour resolution. Starter and up: every streamed pair at the recorded 5-minute resolution, up to the plan's window. For the daily archive use market_history. Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoAlias for pair.
pairNoTrading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted.
hoursNoHow many hours back. Defaults to 24; the ceiling on the free plans is 24, then the plan's history window. Asking for more returns the cap, and the payload says so in `capped`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cappedNoPresent when hours was clamped.
fundingNoFunding points, oldest first, aggregated across venues.
summaryNoThe answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise.
upgradeNoPresent only when the pair or the window is beyond this plan.
availableNoFalse on an uncovered pair, a pair outside the free set keyless, or when no series is recorded.
oi_change_pctNoOpen-interest change first to last point, percent. Absent when either end is missing.
open_interestNoOpen-interest points, oldest first, aggregated across venues.
resolution_minutesNo60 keyless, 5 on a plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hours / description
      Previous value: -"How many hours back. Defaults to 24; keyless ceiling 24, then the plan's flow window. Asking for more returns the cap, and the payload says so in `capped`."New value: +"How many hours back. Defaults to 24; the ceiling on the free plans is 24, then the plan's history window. Asking for more returns the cap, and the payload says so in `capped`."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral details beyond that: aggregation across venues, chronological ordering, resolution by plan tier, and the 'Descriptive market data only' boundary.

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?

The description is compact and front-loaded with the core behavior before moving to usage examples and plan limitations. A little dense in the plan-tier sentence, but no sentence is wasted.

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?

For a simple read-only query tool with three optional parameters and an output schema, the description covers what it is, when to use it, when not to use it, ordering, resolution, and access limits. Nothing essential is missing.

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?

The input schema already covers all three parameters completely (100% coverage), so the baseline applies. The description adds plan-tier context like 'last 24h at 1-hour resolution' but does not need to add schema-level meaning.

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 exactly what the tool returns: 'the intraday path of open interest and funding for one pair, aggregated across venues, oldest first.' It also gives concrete example queries and separates it from market_history, so an agent can tell it apart from its closest sibling.

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 provides explicit use cases ('Use it for ...') and an explicit alternate for a different need ('For the daily archive use market_history'). This is clear when-to-use guidance with an exclusion.

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

All whale-data 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