Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Open interest spikes

get_oi_spike_scan
Read-onlyIdempotent

Open interest spikes across every Bybit USDT perp: abnormal OI jumps against an earlier snapshot of the same universe, at least 30 minutes old and with its exact age returned as baseline_min_ago, plus funding and 24h price context. Costs 0.02 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNotop N, 1-25, default 10

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_oi_spike_scan payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_oi_spike_scan
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_oi_spike_scan payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_oi_spike_scan",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_oi_spike_scan",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive traits. The description adds valuable behavioral context: a cost of 0.02 USDC per call (x402, USDC on Solana/Base) and that it returns baseline_min_ago (exact age of the snapshot) plus funding and 24h price context. This goes beyond annotations without contradiction.

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 a single, information-dense sentence that front-loads the core purpose and scope, then adds details on the baseline, context, and cost. It's efficient but slightly dense; splitting into two sentences would improve readability without adding length.

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 an output schema present and annotations covering safety, the description provides sufficient context: the universe, spike definition, cost, and what the response includes (baseline age, funding, price context). No major gaps for a tool with one optional parameter.

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 has 100% coverage for the single 'limit' parameter, including a full description ('top N, 1-25, default 10'). The tool description doesn't add any parameter-specific meaning beyond the schema, so it stays at the baseline of 3.

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 clearly states the tool scans for open interest spikes across all Bybit USDT perps, defining 'spikes' as abnormal OI jumps against an earlier snapshot. This distinguishes it from siblings like get_open_interest (raw OI levels) and get_funding_* (funding rates) by focusing on anomaly detection with additional context.

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?

The description implies when to use it: when the agent needs a universe-wide scan for OI anomalies with baseline and context. The scope ('across every Bybit USDT perp') and emphasis on 'spikes' differentiate it from single-symbol or raw OI tools, though it doesn't explicitly name alternatives or state exclusions.

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

All AgentFeed 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