Skip to main content
Glama

Emberlane Crypto Intelligence & Agent APIs

Live Funding-Rate Arb & Polymarket Preview

emberlane_alpha_preview
Read-only

Free live preview of the top 3 cross-exchange crypto funding-rate arbitrage spreads (Binance/Bybit/Hyperliquid) and top 3 Polymarket near-expiry high-yield bonds and basket mispricings.

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": "emberlane_alpha_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful un-structured context: 'Free' (no cost/quota barrier), 'live' (real-time freshness), and 'top 3' (result set is deliberately truncated, so the agent should not expect an exhaustive list). Remaining gaps are auth/rate-limit details and whether the sampled data is delayed or illustrative.

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?

A single sentence, front-loaded with the funding-rate arb content and followed by the Polymarket content, with no filler. It is slightly dense — chained noun phrases like 'near-expiry high-yield bonds and basket mispricings' require careful parsing — but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters the call mechanics are fully determined, and the annotations carry the safety profile. But because there is no output schema, the description must convey the return shape, and it only names categories (spreads, bonds, mispricings) without indicating the fields an agent would receive or whether the two sections are returned in one payload.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline of 4 applies. No misleading parameter-like claims appear in the description.

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 names concrete resources with specifics: top 3 cross-exchange funding-rate arbitrage spreads across Binance/Bybit/Hyperliquid, plus top 3 Polymarket near-expiry high-yield bonds and basket mispricings. An agent understands exactly what data this yields. It stops short of differentiating itself from siblings like emberlane_market_pulse_preview or emberlane_scan_token_preview beyond the domain content named.

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?

Calling context is implied by 'preview' and 'top 3' — an agent can infer this is a quick sample lookup, not a comprehensive scan. However, there is no explicit statement of when to prefer this over the sibling preview/scan tools, nor any exclusion such as 'not for historical data' or 'top 3 only, use X for the full list'.

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