Skip to main content
Glama

Emberlane Crypto Intelligence & Agent APIs

Live Crypto & Prediction Market Pulse

emberlane_market_pulse_preview
Read-only

Free summary snapshot of the #1 live perp funding-rate arbitrage spread and #1 Polymarket near-expiry bond, plus direct x402 endpoint details for the full feed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so safety is covered. The description adds that the result is a free summary and includes x402 endpoint details for the full feed, but it does not discuss freshness, rate limits, or how the endpoint details should be used.

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?

The definition is a single dense sentence that front-loads the free summary snapshot and then adds the x402 endpoint detail. There is no redundant or filler wording.

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?

For a no-parameter, read-only preview with no output schema, the description sufficiently states the returned content: top arbitrage spread, top near-expiry bond, and full-feed endpoint details. It could be slightly more complete by clarifying what the x402 endpoint details enable, but the core call is clear.

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?

There are zero input parameters, so there is no parameter semantics to explain; the baseline for a no-param tool is 4. The description does not need to compensate for schema gaps.

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 a concrete output: a free summary snapshot of the top perp funding-rate arbitrage spread and top Polymarket near-expiry bond, plus x402 endpoint details. It is specific about the resource but does not differentiate this preview from sibling preview/scan/list tools.

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?

It implies this is the free preview and that the full feed is reached via x402 endpoint details, which gives some when-to-use context. It does not explicitly say when to choose it over emberlane_alpha_preview, emberlane_scan_token_preview, or emberlane_list_endpoints, nor does it state exclusions.

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