Skip to main content
Glama

Open interest moves

get_oi_moves
Read-only

The perp markets whose open interest (summed across the venues Angler reads) moved most over the last 24 hours, risers and fallers, plus the total change. Rising OI with a price move means new positions; falling OI means positions closing. Markets under $5M of open interest are left out.

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_oi_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many risers and fallers each (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly and closed-world; the description adds real context beyond them: the 24h window, cross-venue aggregation, risers-plus-fallers structure with a total change, and the $5M open-interest cutoff that silently drops small markets. That exclusion is exactly the kind of hidden filtering an agent needs to know.

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?

Three short sentences, front-loaded with what is returned and followed by a short interpretive note and the exclusion rule. No filler, though the interpretation sentence is the least essential.

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?

With no output schema, the description still conveys the return shape (risers, fallers, total change) and the two hidden rules that affect results: the 24h window and the $5M threshold. Only the interaction between limit and risers/fallers is left implicit.

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 the single limit parameter is fully documented there, including its default and 1-25 bound. The description says nothing about how risers and fallers interact with limit, so it adds no meaning over the schema.

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 and metric: perp markets ranked by open-interest change over a defined 24-hour window, aggregated across venues. It's unmistakably distinct from the funding-rate and arb siblings, though it never explicitly names or contrasts an alternative.

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

Usage Guidelines3/5

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

Usage is implied by the framing (find where OI is moving most), but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to a sibling for related questions like price moves or funding.

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