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 Hyperliquid perp: coins whose open interest moved abnormally in the last hour against their own previous day, with the 1h, 4h and 24h change (in coin units, so a price move does not count), a spike z-score, the price move and funding. Read from our own 5-minute sampler: it answers 503 and is never billed until that record is 24 hours deep. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

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.2/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld/non-destructive): it discloses the data source (own 5-minute sampler), an availability constraint (returns 503 until the record is 24 hours deep), and a per-call cost (0.02 USDC via x402 across five chains). That is exactly the operational context an agent needs before calling.

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?

Purpose is front-loaded in the lead clause and no sentence is wasted; every clause adds a distinct fact (scope, units, fields, source, cost). The first sentence is dense with embedded detail but remains readable and information-efficient.

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?

With an output schema present and annotations covering the safety profile, the description fills the remaining gaps an agent needs: what makes a spike, units that isolate OI from price, the sampler's freshness caveat, and the billing model. Complete for a single-parameter, read-only tool.

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?

Only one parameter (limit), fully documented in the schema at 100% coverage, so the schema carries the burden. The description adds nothing about the limit parameter's meaning or defaults, making the baseline 3 correct.

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?

States a specific resource (open interest spikes across every Hyperliquid perp) and precisely scopes it: coins whose open interest moved abnormally in the last hour relative to their own previous day. It then lists the returned fields (1h/4h/24h change in coin units, z-score, price move, funding), which clearly differentiates it from siblings like get_open_interest that return raw levels.

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?

The description makes the use case inferable (surfacing abnormal OI moves), but never explicitly says when to pick this over get_open_interest, get_funding_extremes, or get_squeeze_score. No exclusions or alternative routing are given, so the agent must infer the appropriate context.

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