Skip to main content
Glama

PredMCP

by io.github.RavioleLabs

Get OI History

get_oi_history
Read-only

Open-interest time series for a coin over the last 24h, from our continuous 5-min collector. Hyperliquid has NO OI-history endpoint — this data exists only on predmcp. Includes price + funding at each point. Pro tool get_oi_divergence classifies price-vs-OI regimes (squeeze/liquidation/new positioning) across all coins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCoin, e.g. "BTC" (top ~30 by OI are tracked)
hoursNoLookback window in hours (free tier max: 24)

TDQS

A4.4/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: data comes from a continuous 5-min collector, includes price and funding per point, and is exclusive to predmcp. No contradictions with readOnlyHint and openWorldHint.

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?

Three sentences, front-loaded with core purpose, no wasted words. Each sentence adds value: function, uniqueness, and related tool.

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?

Covers most needs for a simple time series tool: mentions data source, granularity, included fields. Lacks explicit mention of response format or limits, but given simplicity and annotations, it's fairly complete.

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%, but description adds meaning: coin parameter constrained to top ~30 coins by OI, and hours parameter implies lookback with 5-min granularity from continuous collector, which is not in schema.

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?

Description clearly states it provides open-interest time series for a coin over the last 24h with 5-min granularity. It distinguishes from siblings by noting the data is unique to predmcp and mentions a related sibling tool get_oi_divergence.

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?

Implies when to use by stating 'Hyperliquid has NO OI-history endpoint — this data exists only on predmcp,' giving context for its exclusivity. Mentions a pro tool for classification but lacks explicit when-not-to-use instructions.

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

All PredMCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Many tools are specialized, but several pairs have fuzzy boundaries: e.g., get_funding_rates vs get_top_funding_rates, get_basic_macro vs get_macro_context, get_simple_iv vs get_options_iv. An agent could easily select the wrong one.

Naming Consistency4/5

Most tools follow a 'get_X' pattern with descriptive noun phrases. There are a few exceptions like 'create_api_key' and 'search_markets', but overall the convention is consistent and readable.

Tool Count2/5

With 47 tools, the server is overloaded. While the domain is broad, this many tools makes discovery and selection difficult for an agent, reducing coherence.

Completeness5/5

The tool set covers an impressively wide range: macro data, funding, prediction markets, OI history, whale tracking, risk analytics, position sizing, backtesting, and signal generation. It leaves no obvious gaps for a crypto trading assistant.

Resources