Skip to main content
Glama

TallyForge Quant Signals

Perp Funding & Positioning Snapshot

perp_funding_snapshot

Live perpetual-futures positioning for a major crypto asset from Hyperliquid public data: current hourly funding and its annualized rate, 24h and 7d average funding, mark vs oracle basis, open interest and 24h volume in USD, and a crowded-long/short read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "perp_funding_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCrypto ticker quoted in USD on Coinbase, e.g. BTC, ETH, SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the data source ('Hyperliquid public data') and that values are 'Live', which signals a read-only, point-in-time fetch. However, it never states read-only-ness explicitly, says nothing about rate limits, caching/latency, or what happens for a symbol without a Hyperliquid perp market (relevant given the 34-symbol enum), so meaningful behavioral gaps remain.

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?

One sentence, front-loaded with the resource and source, then a clean enumeration of returned fields. No filler, no restatement of the title, and nothing that could be cut without losing information.

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?

There is no output schema, so the description must enumerate return values — and it does so thoroughly, which is the main risk it needed to cover for a single-parameter read tool. What is missing is the operational context (permission-free public read, behavior on unsupported symbols, freshness/polling expectations), which keeps it from a 5.

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 description coverage is 100% and the single parameter carries an enum plus an example, so the schema already does the work. The description adds only the loose framing 'a major crypto asset', which does not clarify the enum's scope (Coinbase-quoted USD tickers) beyond what the schema states. Baseline 3 applies.

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?

The description opens with a specific resource ('Live perpetual-futures positioning') plus the data source (Hyperliquid public data) and then enumerates exactly what is returned: hourly funding and annualized rate, 24h/7d averages, mark vs oracle basis, OI and 24h volume, and a crowding read. That is far more precise than the name alone. It does not explicitly contrast itself with the snapshot siblings (market_regime_snapshot, volatility_snapshot), so it stops short of a 5.

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 only implied by the content: an agent can infer this is the tool for perp funding/positioning questions. There is no explicit statement of when to prefer it over the other *_snapshot siblings, no prerequisites, and no exclusions (e.g. spot-only assets).

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